From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: rsbecker <rsbecker@nexbridge.com>,
"'Chris Judkins-Fisher'" <chris.judkins-fisher@donorschoose.org>,
git@vger.kernel.org
Subject: Re: git whatchanged
Date: Wed, 20 Aug 2025 14:10:11 -0700 [thread overview]
Message-ID: <xmqqsehl8zt8.fsf@gitster.g> (raw)
In-Reply-To: <790a24b0-a799-44dd-b97d-c4c24e5d23a8@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 20 Aug 2025 22:58:18 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> The message itself reads like it could be read like: tell us and we
> might put the brakes on removing it (and that’s it).
Yeah, that is a wrong interpretation we did not want to trigger.
"If you are a developer of a script that uses whatchanged, then
rewrite it with 'log --raw --no-merges' and be happy. If the script
is very widely used, dropping us a note would be nice, as we can
redirect end-user inquiries of your script towards you. If you are
an end-user of such a script, bug your supplier of such a script.
Thanks."
perhaps?
next prev parent reply other threads:[~2025-08-20 21:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 17:51 git whatchanged Chris Judkins-Fisher
2025-08-19 17:59 ` Chris Judkins-Fisher
2025-08-19 20:57 ` rsbecker
2025-08-20 7:52 ` Kristoffer Haugsbakk
2025-08-20 14:12 ` rsbecker
2025-08-20 16:49 ` Junio C Hamano
2025-08-20 17:05 ` Chris Judkins-Fisher
2025-08-20 20:58 ` Kristoffer Haugsbakk
2025-08-20 21:10 ` Junio C Hamano [this message]
2025-08-20 21:11 ` Kristoffer Haugsbakk
-- strict thread matches above, loose matches on Subject: below --
2025-08-26 13:04 Chris Palmer
2025-08-26 13:54 ` Kristoffer Haugsbakk
2025-09-03 15:34 Jesse Hathaway
2025-09-03 19:56 ` Junio C Hamano
2025-09-03 20:43 ` Kristoffer Haugsbakk
2025-09-03 21:47 ` Junio C Hamano
2025-09-04 23:45 Michael Tourigny (TERAWE CORPORATION)
2025-09-10 20:49 Jose Jaramillo
2025-09-10 21:03 ` Kristoffer Haugsbakk
2025-09-10 21:15 ` Jose Jaramillo
2025-09-26 1:00 Neal Miller
2025-09-26 7:13 ` Kristoffer Haugsbakk
2025-09-26 15:54 ` Junio C Hamano
2025-09-28 1:12 ` Neal Miller
2025-10-02 6:48 Jiří Bašek
2025-10-02 7:12 ` Kristoffer Haugsbakk
2025-10-08 14:20 Git whatchanged Filippo Falezza
2025-10-08 14:42 ` Kristoffer Haugsbakk
2025-10-13 12:44 git whatchanged Grzegorz Koperwas
2025-10-13 13:47 ` Kristoffer Haugsbakk
2025-10-16 12:16 Julian Squires
2025-10-16 13:27 ` Kristoffer Haugsbakk
2025-10-31 8:02 Remke Schuurmans
2025-10-31 8:23 ` Kristoffer Haugsbakk
[not found] ` <c2551c49-bcb4-4518-97d3-063941d591e8@gmail.com>
2025-10-31 9:13 ` Kristoffer Haugsbakk
2025-11-07 11:40 Franz Brauße
2025-11-07 13:11 ` Kristoffer Haugsbakk
2025-11-07 14:16 ` Franz Brauße
2025-11-07 14:30 ` 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=xmqqsehl8zt8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chris.judkins-fisher@donorschoose.org \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=rsbecker@nexbridge.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;
as well as URLs for NNTP newsgroup(s).