From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: Ejecting things more aggressively out of 'seen'?
Date: Tue, 03 Nov 2026 08:04:55 -0800 [thread overview]
Message-ID: <xmqqbj85c34o.fsf@gitster.g> (raw)
In-Reply-To: <aumNkxzE7wfa519p@pks.im> (Patrick Steinhardt's message of "Tue, 3 Nov 2026 08:30:27 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> The question that newcomers often have here is whether they need to do
> anything about this. They basically wonder whether that question is
> directed at them specifically. Maybe rewording it to "Will merge to next
> [on <day>] unless told otherwise" may help clarify?
That is quite a mouthful and [on <day>] is harder to automate, so
I'd probably keep the '?' and describe what it means near the top,
where I already talk about what it means to be in 'next' etc.
next prev parent reply other threads:[~2026-11-03 16:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 3:09 What's cooking in git.git (Jul 2026, #12) Junio C Hamano
2026-07-29 13:24 ` Phillip Wood
2026-07-29 14:18 ` Junio C Hamano
2026-07-29 15:20 ` Phillip Wood
2026-07-29 17:48 ` Junio C Hamano
2026-08-05 13:10 ` Phillip Wood
2026-08-05 17:03 ` Junio C Hamano
2026-11-02 7:31 ` Ejecting things more aggressively out of 'seen'? Junio C Hamano
2026-11-02 9:59 ` Patrick Steinhardt
2026-11-02 16:17 ` Junio C Hamano
2026-11-02 16:34 ` Phillip Wood
2026-11-03 7:30 ` Patrick Steinhardt
2026-11-03 16:04 ` Junio C Hamano [this message]
2026-11-03 19:29 ` Junio C Hamano
2026-07-31 6:20 ` What's cooking in git.git (Jul 2026, #12) Matt Hunter
2026-07-31 15:36 ` Junio C Hamano
2026-07-30 6:11 ` Harald Nordgren
2026-07-31 7:02 ` Matt Hunter
2026-08-03 9:05 ` Phillip Wood
2026-08-03 16:02 ` Junio C Hamano
2026-08-04 13:19 ` Phillip Wood
2026-08-03 9:11 ` Phillip Wood
2026-07-29 15:14 ` Phillip Wood
2026-07-29 15:52 ` 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=xmqqbj85c34o.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.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