From: Derrick Stolee <stolee@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] Move libgit.a sources into separate "lib/" directory
Date: Tue, 21 Apr 2026 10:13:31 -0400 [thread overview]
Message-ID: <4199e58b-d0fc-4240-9717-16c89ae73322@gmail.com> (raw)
In-Reply-To: <aecRW_nwBVM21CPF@pks.im>
On 4/21/2026 1:55 AM, Patrick Steinhardt wrote:
> On Mon, Apr 20, 2026 at 08:03:44AM -0400, Derrick Stolee wrote:
Thanks for your thoughts on the earlier parts of my message. I think
you're moving in the right direction and I don't have further comments.
>> Did you consider moving these files, too?
>
> My initial version was moving around remaining ".c", ".sh" and ".perl"
> files, as well. These are (almost) all related to top-level commands
> commands, so I was handling those by introducing a new "bin/" directory
> and moving them in there.
...
> So I still lean into the direction of doing things one step at a time,
> because it focusses the discussion, and every subsequent step is
> significantly smaller. But if it helps I wouldn't mind also going the
> extra mile.
Upon reconsideration, the files that are left probably have less churn
in the core project, so are less problematic to shift to a new directory
as an independent update.
I think the forks are more likely to have issues with these core files,
especially when they add new commands in git.c. But it's still probably
better to reduce risk wherever possible and this is one way to isolate
the risk.
Thanks,
-Stolee
next prev parent reply other threads:[~2026-04-21 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 13:24 [PATCH RFC 0/2] Move libgit.a sources into separate "lib/" directory Patrick Steinhardt
2026-04-16 13:24 ` [PATCH RFC 1/2] t/helper: prepare "test-example-tap.c" for introduction of "lib/" Patrick Steinhardt
2026-04-16 13:24 ` [PATCH RFC 2/2] Move libgit.a sources into separate "lib/" directory Patrick Steinhardt
2026-04-17 17:08 ` Elijah Newren
2026-04-17 19:18 ` brian m. carlson
2026-04-17 21:18 ` Junio C Hamano
2026-04-17 21:51 ` brian m. carlson
2026-04-20 6:41 ` Patrick Steinhardt
2026-04-19 14:11 ` [PATCH RFC 0/2] " Phillip Wood
2026-04-20 6:41 ` Patrick Steinhardt
2026-04-20 12:03 ` Derrick Stolee
2026-04-21 5:55 ` Patrick Steinhardt
2026-04-21 14:13 ` Derrick Stolee [this message]
2026-04-22 6:39 ` Patrick Steinhardt
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=4199e58b-d0fc-4240-9717-16c89ae73322@gmail.com \
--to=stolee@gmail.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