From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v2] you_still_use_that(): reword the instructions
Date: Wed, 26 Aug 2026 10:48:29 -0700 [thread overview]
Message-ID: <xmqqjypchixe.fsf@gitster.g> (raw)
In-Reply-To: <xmqqo6epj6is.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 26 Aug 2026 07:33:31 -0700")
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 <gitster@pobox.com>
---
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 <git@vger.kernel.org> 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"
+ " https://lore.kernel.org/git/?q=%s\n\n"
+ "- Send an email to <git@vger.kernel.org> asking for help, only if\n"
+ " suggestions by others do not work for you.\n"
"\n"),
percent_encoded.buf);
strbuf_release(&percent_encoded);
next prev parent reply other threads:[~2026-08-26 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 14:33 [PATCH] you_still_use_that(): reword the instructions Junio C Hamano
2026-08-26 16:04 ` Michael Montalbo
2026-08-26 17:00 ` Junio C Hamano
2026-08-26 17:12 ` Michael Montalbo
2026-08-26 17:36 ` Michael Montalbo
2026-08-26 17:45 ` Junio C Hamano
2026-08-26 17:48 ` Michael Montalbo
2026-08-26 16:06 ` Michael Montalbo
2026-08-26 16:23 ` Junio C Hamano
2026-08-26 17:48 ` Junio C Hamano [this message]
2026-08-27 1:22 ` [PATCH v2] " Elijah Newren
2026-08-27 6:49 ` Kristoffer Haugsbakk
2026-08-27 14:38 ` Junio C Hamano
2026-08-27 16:01 ` Junio C Hamano
2026-08-27 18:15 ` [PATCH v3] " Junio C Hamano
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=xmqqjypchixe.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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