From: Junio C Hamano <gitster@pobox.com>
To: Michael Montalbo <mmontalbo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] you_still_use_that(): reword the instructions
Date: Wed, 26 Aug 2026 09:23:48 -0700 [thread overview]
Message-ID: <xmqqv78wj1ez.fsf@gitster.g> (raw)
In-Reply-To: <CAC2Qwm+Gg3nhxtwhQjrvrk6Pm_R=XEpAwYxVKqT0Ps9UZ-DAyg@mail.gmail.com> (Michael Montalbo's message of "Wed, 26 Aug 2026 09:06:56 -0700")
Michael Montalbo <mmontalbo@gmail.com> writes:
> On Wed, Aug 26, 2026 at 7:33 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> 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"
>
> I noticed there are now two newlines at the end instead of one like before. Same
> for the lore link below. Is that intentional?
Absolutely.
>
>> + "- 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 16:23 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 [this message]
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=xmqqv78wj1ez.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mmontalbo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.