All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Mark Waite <mark.earl.waite@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Jenkins still uses 'git whatchanged'
Date: Mon, 18 Aug 2025 18:52:29 -0700	[thread overview]
Message-ID: <xmqqcy8sgjs2.fsf@gitster.g> (raw)
In-Reply-To: <CAO49JtHLs0yCAmNX-2VO=0mC-u4JKPWw86Lg+xe1pV6Dr6YZWw@mail.gmail.com> (Mark Waite's message of "Mon, 18 Aug 2025 17:45:26 -0600")

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.

  reply	other threads:[~2025-08-19  1:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 23:45 Jenkins still uses 'git whatchanged' Mark Waite
2025-08-19  1:52 ` Junio C Hamano [this message]
2025-08-19  3:00   ` Mark Waite

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=xmqqcy8sgjs2.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mark.earl.waite@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.