From: Patrick Steinhardt <ps@pks.im>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [-SPAM-] What's cooking in git.git (Jul 2025, #03; Wed, 9)
Date: Fri, 11 Jul 2025 10:49:00 +0200 [thread overview]
Message-ID: <aHDP_GK0ytKkp_3n@pks.im> (raw)
In-Reply-To: <61a9185d-8ed8-4794-8f7e-1ed64503cc62@ramsayjones.plus.com>
On Thu, Jul 10, 2025 at 10:44:07PM +0100, Ramsay Jones wrote:
> On 10/07/2025 22:12, Junio C Hamano wrote:
> > Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
> >
> >>
> >> How would you like to proceed? (yes, I haven't written the commit message
> >> yet).
> >
> > ... appears near the end of the message, and the way _I_ would like
> > to proceed is to make sure two parties involved in overlapping
> > solutions to the same problem talk to each other and come up with a
> > solution together. The first step to get you going would be to CC
> > the other parties involved.
>
> Oops, I had intended to cc Patrick! :(
>
> > If the controversial step in Patrick's 8-patch series is relatively
> > independent from others (which was the impression I got from "more
> > or less random cleanups and improvements"), one approach with less
> > friction is to simply omit it and make it 7-patch series. While you
> > and Patric work out what the best approach to solve the libexecdir
> > problem, the rest of the series can proceed without waiting,
> > hopefully?
>
> Yep, that would be my preferred route.
>
> Having said that, Patrick's patch does remove the regression, so we
> could keep them separate if that is preferred. I don't mind either
> way. :)
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?
Thanks!
Patrick
next prev parent reply other threads:[~2025-07-11 8:49 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 [this message]
2025-07-11 15:00 ` Junio C Hamano
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=aHDP_GK0ytKkp_3n@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).