From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2025, #08; Tue, 28)
Date: Wed, 29 Jan 2025 13:34:39 -0800 [thread overview]
Message-ID: <xmqq1pwli9sg.fsf@gitster.g> (raw)
In-Reply-To: <xmqqr04lk98n.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 29 Jan 2025 06:03:36 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Patrick Steinhardt <ps@pks.im> writes:
>
>> On Tue, Jan 28, 2025 at 04:18:00PM -0800, Junio C Hamano wrote:
>>> * ps/ci-misc-updates (2025-01-10) 10 commits
>>> ...
>>>
>>> CI updates (containerization, dropping stale ones, etc.).
>>>
>>> Will merge to 'master'.
>>> source: <20250110-b4-pks-ci-fixes-v4-0-6e4613446080@pks.im>
>>
>> I'm a bit confused about the state of this topic. You say it will be
>> merged to 'master', but as far as I can see it's not even part of 'next'
>> yet.
>
> I am utterly confused---I'll figure out what happened here.
This turns out to be a simple typo where I meant to say "next" and
typed "master". I was worried about something worse, like
accicentally removing one entry that was ready to be merged to
'master' that happened to be listed immediately after this one.
Thanks for noticing.
next prev parent reply other threads:[~2025-01-29 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 0:18 What's cooking in git.git (Jan 2025, #08; Tue, 28) Junio C Hamano
2025-01-29 7:57 ` Patrick Steinhardt
2025-01-29 14:03 ` Junio C Hamano
2025-01-29 21:34 ` Junio C Hamano [this message]
2025-01-30 5:43 ` Patrick Steinhardt
2025-01-31 23:30 ` Jeff King
2025-02-03 6:08 ` Patrick Steinhardt
2025-02-03 21:32 ` Junio C Hamano
2025-01-31 17:51 ` 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=xmqq1pwli9sg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).