From: jorg@ml1.net
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Still using "git whatchanged"
Date: Wed, 03 Sep 2025 10:15:18 +0300 [thread overview]
Message-ID: <a80907d3-0dfd-4e68-818d-4092a2855848@app.fastmail.com> (raw)
In-Reply-To: <049579fb-6e42-4c3c-ba5c-71c5f843a66e@app.fastmail.com>
On Wed, Sep 3, 2025, at 10:08, Kristoffer Haugsbakk wrote:
> On Wed, Sep 3, 2025, at 08:11, jorg@ml1.net wrote:
>>
>> Given the circumstances, I vote for keeping "git whatchanged".
>
> You can see the discussion around the whatchanged deprecation as well as
> other things in this document:
>
> https://git-scm.com/docs/BreakingChanges.html
I fail to find the discussion around the whatchanged deprecation in that document. There is mention of the deprecation, but that's all.
(But I can certainly find discussion around it if I want to, no need to send more links.)
>> Given the circumstances,
>
> What circumstances?
The circumstances that other changes to command line parameters (which might mitigate the loss of "whatchanged") are not up for debate.
Regards,
J
next prev parent reply other threads:[~2025-09-03 7:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 6:18 Still using "git whatchanged" jorg
2025-09-02 16:29 ` Junio C Hamano
2025-09-02 16:38 ` jorg
2025-09-02 20:33 ` Junio C Hamano
2025-09-03 6:11 ` jorg
2025-09-03 7:08 ` Kristoffer Haugsbakk
2025-09-03 7:15 ` jorg [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-15 5:42 still using 'git whatchanged' Greg Couch
2025-10-15 7:22 ` Kristoffer Haugsbakk
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=a80907d3-0dfd-4e68-818d-4092a2855848@app.fastmail.com \
--to=jorg@ml1.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kristofferhaugsbakk@fastmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox