From: Elijah Newren Date: Thu, 27 Aug 2026 01:22:54 GMT Subject: Re: [PATCH v2] you_still_use_that(): reword the instructions Message-ID: In-Reply-To: On Wed, Aug 26, 2026 at 10:50 AM Junio C Hamano wrote: > > The message is overly long and may mislead readers into thinking > there is recourse other than adopting the new workflow. Clarify > that the message is there merely to help them find a replacement > workflow, and is not offering to reconsider a decision that has > already taken effect. > > Signed-off-by: Junio C Hamano > --- > usage.c | 16 +++++++--------- > 1 file changed, 7 insertions(+), 9 deletions(-) > > diff --git c/usage.c w/usage.c > index 3f0118ab2a..365c0bcb90 100644 > --- c/usage.c > +++ w/usage.c > @@ -386,21 +386,19 @@ NORETURN void you_still_use_that(const char *command_name, const char *hint) > STRBUF_ENCODE_SLASH); > > fprintf(stderr, > - _("'%s' is nominated for removal.\n"), command_name); > + _("'%s' will be removed soon.\n"), command_name); > > if (hint) > fputs(hint, stderr); > > fprintf(stderr, > - _("If you still use this command, here's what you can do:\n" > + _("If you need a replacement:\n" > "\n" > - "- read https://git-scm.com/docs/BreakingChanges.html\n" > - "- check if anyone has discussed this on the mailing\n" > - " list and if they came up with something that can\n" > - " help you: https://lore.kernel.org/git/?q=%s\n" > - "- send an email to to let us\n" > - " know that you still use this command and were unable\n" > - " to determine a suitable replacement\n" > + "- Read https://git-scm.com/docs/BreakingChanges.html.\n\n" > + "- Check what others on the mailing suggest as a replacement:\n" missing "list"? ("mailing [list] suggest") > + " https://lore.kernel.org/git/?q=%s\n\n" > + "- Send an email to asking for help, only if\n" > + " suggestions by others do not work for you.\n" > "\n"), > percent_encoded.buf); > strbuf_release(&percent_encoded); Otherwise, looks good.