From: Patrick Steinhardt <ps@pks.im>
To: phillip.wood@dunelm.org.uk
Cc: git@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] Move libgit.a sources into separate "lib/" directory
Date: Mon, 20 Apr 2026 08:41:27 +0200 [thread overview]
Message-ID: <aeXKl0tUDvlkoHhA@pks.im> (raw)
In-Reply-To: <ef096525-d2d8-47d4-be8f-75236ceeb3c6@gmail.com>
On Sun, Apr 19, 2026 at 03:11:54PM +0100, Phillip Wood wrote:
> Hi Patrick
>
> On 16/04/2026 14:24, Patrick Steinhardt wrote:
> > Hi,
> >
> > this small patch series follows up on a discussion we had two years ago
> > during the Git Contributor's Summit in Berlin.
> >
> > I'm fully aware that this will likely result in some discussion, which
> > is why I have labelled this as RFC. I'd be fine with a result of "let's
> > not do it" if we cannot agree on this step, but I think that the current
> > layout hurts discoverability quite a bit. Not only for newcomers, but
> > I'm also struggling with it quite frequently.
>
> I think it makes sense to have all the sources for libgit.a in their own
> directory as it is easier to say things like "please try to avoid new uses
> of 'the_repository' and prefer 'error()' over 'die()' in library code" if
> all the library code is in the same directory. I'm not really convinced it
> helps with discovery though as there are just as many files and now there
> are more subdirectories to trawl through to find what you're looking for. I
> think the anwser to that problem is "use 'git grep' or 'ctags' etc."
Agreed, it doesn't help with discoverability in "lib/" itself, as
there's still going to be a bunch of files in there. My main intent here
is to help with discoverability in the top-level directory, which is the
main entry point for everyone.
Patrick
next prev parent reply other threads:[~2026-04-20 6:41 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 [this message]
2026-04-20 12:03 ` Derrick Stolee
2026-04-21 5:55 ` Patrick Steinhardt
2026-04-21 14:13 ` Derrick Stolee
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=aeXKl0tUDvlkoHhA@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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