From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: Subject: [PATCH 0/2] misc Makefile patches
Date: Wed, 17 Jul 2024 21:50:22 -0700 [thread overview]
Message-ID: <xmqqle1z1ey9.fsf@gitster.g> (raw)
In-Reply-To: <7a38d869-8d8a-4922-894c-59ac7fc20449@ramsayjones.plus.com> (Ramsay Jones's message of "Thu, 18 Jul 2024 02:10:48 +0100")
Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
> These patches have been hanging around for _years_, so I rebased them
> onto the current master branch @ 04f5a52757 ("Post 2.46-rc0 batch #2",
> 2024-07-16). This was prompted by the sparse discussion tonight.
I do not see any immediate downside, but lack of immediate upside
matters a lot more at this phase in the cycle. I may queue them but
neither looks worth disrupting the upcoming release. So it would
have to wait before the 2.46 final before it hits the 'master'
track.
Thanks.
prev parent reply other threads:[~2024-07-18 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 1:10 Subject: [PATCH 0/2] misc Makefile patches Ramsay Jones
2024-07-18 4:50 ` 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=xmqqle1z1ey9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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;
as well as URLs for NNTP newsgroup(s).