From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
Cc: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org, "Patrick Steinhardt" <ps@pks.im>,
"Taylor Blau" <me@ttaylorr.com>
Subject: Re: [PATCH] t1400: fix --no-create-reflog test and description
Date: Fri, 08 Nov 2024 12:13:51 +0900 [thread overview]
Message-ID: <xmqqwmhepgcw.fsf@gitster.g> (raw)
In-Reply-To: <4e68a04f-fb5e-49f9-8ba2-661027d8165d@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 07 Nov 2024 13:11:15 +0100")
"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:
> I didn’t get the impression that this is expecting a reroll. But I
> haven’t seen it mentioned or applied to `seen`/`next`?
If the interim maintainer did not think it is ready to be queued to
'seen', I won't go back to the list archive to pick it up (after
all, that is part of trusting interim maintainer is about---otherwise
I have to go back and consume all the list backlog, which does not
make sense).
If a topic is worth resurrecting, do resend it for discussion.
Looking at the archived discussion (for this topic I am making an
exception), I did not get an impression that this got a "yeah this
is a good thing to do" support, only a lukewarm "it may be a
starting point in a good direction".
Thanks.
prev parent reply other threads:[~2024-11-08 3:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 16:12 [PATCH] t1400: fix --no-create-reflog test and description kristofferhaugsbakk
2024-10-21 12:08 ` Patrick Steinhardt
2024-10-21 16:48 ` Kristoffer Haugsbakk
2024-10-21 19:02 ` Taylor Blau
2024-10-21 21:02 ` Kristoffer Haugsbakk
2024-10-21 21:10 ` Taylor Blau
2024-11-07 12:11 ` Kristoffer Haugsbakk
2024-11-08 3:13 ` Junio C Hamano [this message]
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=xmqqwmhepgcw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=me@ttaylorr.com \
--cc=ps@pks.im \
/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;
as well as URLs for NNTP newsgroup(s).