From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>, git@vger.kernel.org
Subject: Re: [-SPAM-] What's cooking in git.git (Jul 2025, #03; Wed, 9)
Date: Fri, 11 Jul 2025 08:00:57 -0700 [thread overview]
Message-ID: <xmqq34b24vrq.fsf@gitster.g> (raw)
In-Reply-To: <aHDP_GK0ytKkp_3n@pks.im> (Patrick Steinhardt's message of "Fri, 11 Jul 2025 10:49:00 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> I'm happy to just drop the patch and let you handle the regression.
>
> There aren't any dependencies between the patches in this series, so
> it's as easy as removing the patch. Junio, do you want me to resend the
> series with the patch dropped or will you drop the patch on your side?
Will do. As always, thanks for working well together.
next prev parent reply other threads:[~2025-07-11 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 8:03 What's cooking in git.git (Jul 2025, #03; Wed, 9) Junio C Hamano
2025-07-10 19:32 ` [-SPAM-] " Ramsay Jones
2025-07-10 21:12 ` Junio C Hamano
2025-07-10 21:44 ` Ramsay Jones
2025-07-11 8:49 ` Patrick Steinhardt
2025-07-11 15:00 ` Junio C Hamano [this message]
2025-07-11 15:39 ` Ramsay Jones
2025-07-15 23:32 ` [PATCH 0/2] meson regression fix Ramsay Jones
2025-07-15 23:32 ` [PATCH 1/2] meson: fix installation when -Dlibexexdir is set Ramsay Jones
2025-07-15 23:32 ` [PATCH 2/2] po/meson.build: add missing 'ga' language code Ramsay Jones
2025-07-11 0:07 ` "What's cooking" incremental update report Junio C Hamano
2025-07-11 2:05 ` What's cooking in git.git (Jul 2025, #03; Wed, 9) Ayush Chandekar
2025-07-11 16:01 ` Junio C Hamano
2025-07-11 18:15 ` Ayush Chandekar
2025-07-11 18:34 ` 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=xmqq34b24vrq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--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).