* Jenkins still uses 'git whatchanged'
@ 2025-08-18 23:45 Mark Waite
2025-08-19 1:52 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Mark Waite @ 2025-08-18 23:45 UTC (permalink / raw)
To: Git Users
Git 2.51.0 has deprecated the 'whatchanged' command. The git client
plugin for Jenkins still uses the "git whatchanged" command to generate
its changelog.
I hope to release a replacement soon, but am only starting the
implementation now.
Mark Waite
Message sent as requested by git 2.51.0
'git whatchanged' is nominated for removal.
If you still use this command, please add an extra
option, '--i-still-use-this', on the command line
and let us know you still use it by sending an e-mail
to <git@vger.kernel.org>. Thanks.
fatal: refusing to run without --i-still-use-this
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Jenkins still uses 'git whatchanged'
2025-08-18 23:45 Jenkins still uses 'git whatchanged' Mark Waite
@ 2025-08-19 1:52 ` Junio C Hamano
2025-08-19 3:00 ` Mark Waite
0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2025-08-19 1:52 UTC (permalink / raw)
To: Mark Waite; +Cc: Git Users
Mark Waite <mark.earl.waite@gmail.com> writes:
> Git 2.51.0 has deprecated the 'whatchanged' command. The git client
> plugin for Jenkins still uses the "git whatchanged" command to generate
> its changelog.
>
> I hope to release a replacement soon, but am only starting the
> implementation now.
>
> Mark Waite
>
> Message sent as requested by git 2.51.0
>
> 'git whatchanged' is nominated for removal.
> If you still use this command, please add an extra
> option, '--i-still-use-this', on the command line
> and let us know you still use it by sending an e-mail
> to <git@vger.kernel.org>. Thanks.
> fatal: refusing to run without --i-still-use-this
Thanks for letting us know.
Please note that "--i-still-use-this" is merely for you to buy some
time while you update your ware to rewrite your use of whatchanged
with something else (probably "git log --raw" with some other
options). When you update to Git 3.0, whose release date is not yet
even known, whatchanged will no longer be available with or without
that option.
Unless we hear so many reports from those who needed to work around
with "--i-still-use-this" and realize that removal of that command
is unfeasible, that is.
Thanks again.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Jenkins still uses 'git whatchanged'
2025-08-19 1:52 ` Junio C Hamano
@ 2025-08-19 3:00 ` Mark Waite
0 siblings, 0 replies; 3+ messages in thread
From: Mark Waite @ 2025-08-19 3:00 UTC (permalink / raw)
To: Junio C Hamano; +Cc: Git Users
On Mon, Aug 18, 2025 at 7:52 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Thanks for letting us know.
>
> Please note that "--i-still-use-this" is merely for you to buy some
> time while you update your ware to rewrite your use of whatchanged
> with something else (probably "git log --raw" with some other
> options). When you update to Git 3.0, whose release date is not yet
> even known, whatchanged will no longer be available with or without
> that option.
Thanks very much. The implementation is looking good. I expect the
new release of the git client plugin will be ready this week. The code
changes were simple and the test results are all positive.
Mark Waite
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-08-19 3:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-18 23:45 Jenkins still uses 'git whatchanged' Mark Waite
2025-08-19 1:52 ` Junio C Hamano
2025-08-19 3:00 ` Mark Waite
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.