From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #06; Mon, 15)
Date: Tue, 16 Sep 2025 22:54:06 +0200 [thread overview]
Message-ID: <c0f1e08a-afe1-4cfd-af11-aa07ed458570@app.fastmail.com> (raw)
In-Reply-To: <xmqqtt13frqm.fsf@gitster.g>
On Mon, Sep 15, 2025, at 21:19, Junio C Hamano wrote:
> * kh/you-still-use-whatchanged-fix (2025-09-14) 8 commits
> - BreakingChanges: remove claim about whatchanged reports
> - whatchanged: remove not-even-shorter clause
> - whatchanged: hint about git-log(1) and aliasing
> - you-still-use-that??: help the user help themselves
> - t0014: test shadowing of aliases for a sample of builtins
> - git: allow alias-shadowing deprecated builtins
> - git: move seen-alias bookkeeping into handle_alias(...)
> - git: add `deprecated` category to --list-cmds
>
> Update "do you still use it?" message given by a command that is
> deeply deprecated and allow us to suggest alternatives.
>
> Ready?
> source: <cover.1757879060.git.code@khaugsbakk•name>
I need to make a new version for the extra output line.[1] I was
planning on doing it today but your message about
`WITH_BREAKING_CHANGES=YesPlease` prompted me to investigate that.[2]
[1]: https://lore.kernel.org/git/7d63af22-3886-4dcf-863e-dec333601b3b@app.fastmail.com/
[2]: https://lore.kernel.org/git/cover.1757446619.git.code@khaugsbakk.name/T/#m665486896912338c381f2b63003358111c7a2ea2
Cheers and good night
prev parent reply other threads:[~2025-09-16 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 19:19 What's cooking in git.git (Sep 2025, #06; Mon, 15) Junio C Hamano
2025-09-16 6:53 ` Patrick Steinhardt
2025-09-16 16:16 ` Junio C Hamano
2025-09-16 16:49 ` Jeff King
2025-09-16 17:19 ` Junio C Hamano
2025-09-18 5:52 ` Patrick Steinhardt
2025-09-16 20:54 ` Kristoffer Haugsbakk [this message]
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=c0f1e08a-afe1-4cfd-af11-aa07ed458570@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/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