Git development
 help / color / mirror / Atom feed
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 10:45:18 -0700	[thread overview]
Message-ID: <xmqqwltchj2p.fsf@gitster.g> (raw)
In-Reply-To: <CAC2Qwm+Dx1UxLO3EOkQ-9uBokxacVfgrs7+XCj3BeM9vt8HcPw@mail.gmail.com> (Michael Montalbo's message of "Wed, 26 Aug 2026 10:12:13 -0700")

Michael Montalbo <mmontalbo@gmail.com> writes:

> On Wed, Aug 26, 2026 at 10:00 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Michael Montalbo <mmontalbo@gmail.com> writes:
>>
>> > I think this change makes sense.
>> >
>> >> +                 "- Send an email to <git@vger.kernel.org> asking for help, only if\n"
>> >> +                 "  suggestions by others do not work for you.\n"
>> >
>> > Maybe a slight reword to reinforce the idea that the command is not coming
>> > back:
>> >
>> >   "Send an email... asking for help, only if suggested replacements
>> >     for the [now?] deprecated command do not work for you."
>> ...
> Adding something like "[now] deprecated" or otherwise more explicitly
> suggesting the command does not intend to return is my main feedback.

The same function emits a message that says "this command is
nominated for removal."  Perhaps we want to strengthen that part by
saying "will be removed" instead?

  parent reply	other threads:[~2026-08-26 17:45 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 [this message]
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=xmqqwltchj2p.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox