Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH] you_still_use_that(): reword the instructions
Date: Wed, 26 Aug 2026 07:33:31 -0700	[thread overview]
Message-ID: <xmqqo6epj6is.fsf@gitster.g> (raw)

The message is overly long and may mislead readers into thinking
there is recourse other than adopting the new workflow.  Clarify
that it merely helps them find a replacement, rather than offering
to reconsider a decision that has already taken effect.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 usage.c | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git c/usage.c w/usage.c
index 3f0118ab2a..9933b9911c 100644
--- c/usage.c
+++ w/usage.c
@@ -392,15 +392,13 @@ NORETURN void you_still_use_that(const char *command_name, const char *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);

             reply	other threads:[~2026-08-26 14:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 14:33 Junio C Hamano [this message]
2026-08-26 16:04 ` [PATCH] you_still_use_that(): reword the instructions 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 ` [PATCH v2] " Junio C Hamano
2026-08-27  1:22   ` 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=xmqqo6epj6is.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