Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org,  "Michael Montalbo" <mmontalbo@gmail.com>,
	 "Elijah Newren" <newren@gmail.com>
Subject: Re: [PATCH v2] you_still_use_that(): reword the instructions
Date: Thu, 27 Aug 2026 09:01:08 -0700	[thread overview]
Message-ID: <xmqqecfjbliz.fsf@gitster.g> (raw)
In-Reply-To: <cd741511-b457-4464-aab0-56d8554bf763@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 27 Aug 2026 08:49:27 +0200")

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

> I was thinking that maybe the final bullet point could say something
> like
>
>      ... and don’t send a message voting for it to come back because the
>      decision has already been made
>
> But it *could* be mentioned here instead. “The decision is final ...”
> ...
> And I also bring this up because the commit message says:
>
>      and [the message] is not offering to reconsider a decision that has
>      already taken effect.

I forgot to respond to this part.  Yes, we could be more blunt and
explicitly state that bringing the issue back to the discussion
stage is way too late and unwelcome.

However, offering advice only on finding a replacement should be a
sufficient hint for any reasonably clueful person to understand that
it is far too late to suggest a reversal.  There will always be
those who demand that we revisit our decisions regardless of what we
tell them, and those people are unsalvageable.

  parent reply	other threads:[~2026-08-27 16:01 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 ` [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 [this message]
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=xmqqecfjbliz.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=mmontalbo@gmail.com \
    --cc=newren@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