From: <rsbecker@nexbridge•com>
To: <git@vger•kernel.org>
Subject: Git whatchanged --i-still-use-this breaks Jenkins GitSCM
Date: Thu, 21 Aug 2025 09:59:36 -0400 [thread overview]
Message-ID: <020001dc12a3$d7c392c0$874ab840$@nexbridge.com> (raw)
The requirement to add --i-still-use-this for git whatchanged in 2.51.0 is
currently generating
errors in Jenkins GitSCM, which, unfortunately, still uses that command. I
have reported this
as an issue to that team.
It seems to me that we could have some .gitconfig option, maybe
core.ignoreDeprecations=true or core.iReallyMeanIt=true to suppress the
requirement
to provide this option on the CLI because of unintended consequences.
Note: There does not seem to be a way to add the option in Jenkins.
--Randall
--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.
reply other threads:[~2025-08-21 13:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='020001dc12a3$d7c392c0$874ab840$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox