From: John Keeping <john@keeping.me.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
Duy Nguyen <pclouds@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [RFC] Code reorgnization
Date: Thu, 17 Mar 2016 21:43:55 +0000 [thread overview]
Message-ID: <20160317214355.GA32317@serenity.lan> (raw)
In-Reply-To: <xmqqy49gzzrf.fsf@gitster.mtv.corp.google.com>
On Thu, Mar 17, 2016 at 12:10:44PM -0700, Junio C Hamano wrote:
> Stefan Beller <sbeller@google.com> writes:
>
> > For now I would just go with 3 directories:
> >
> > non-git/ (or util, helpers, or anything that could be ripped out and be useful
> > e.g. strbufs, argv-array run-command, lockfile
> > git/ (maybe called lib? All stuff that is pure Git and is used for libgit
> >
> > builtin/ (as we have it today + all that stuff that doesn't go into
> > git/ very well?)
>
> It is unclear where you want to have standalone programs in the
> above. I'd say lib/ and src/ for the first two, where lib/ is for
> things that could be lifted without any Git dependencies and src/
> for everything else.
>
> Aren't there some folks who link directly with our codebase (I am
> thinking about cgit, but hjemli.net/git/cgit does not seem to be
> responding anymore)?
CGit lives at https://git.zx2c4.com/cgit/ these days.
The organisation of the git code shouldn't make a difference since CGit
just links with libgit.a, even if it does CGit pulls in git.git as a
submodule so it can just fix any problems in the same commit that
updates the submodule reference.
next prev parent reply other threads:[~2016-03-17 21:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 11:11 [RFC] Code reorgnization Duy Nguyen
2016-03-17 13:32 ` Johannes Schindelin
2016-03-17 13:35 ` Duy Nguyen
2016-03-17 16:21 ` Junio C Hamano
2016-03-17 17:00 ` Thomas Adam
2016-03-17 17:48 ` Junio C Hamano
2016-03-17 18:37 ` Stefan Beller
2016-03-17 19:10 ` Junio C Hamano
2016-03-17 21:03 ` Pranit Bauva
2016-03-17 21:43 ` John Keeping [this message]
2016-03-17 21:49 ` Junio C Hamano
2016-03-18 0:28 ` Duy Nguyen
2016-03-18 5:24 ` Jeff King
2016-03-18 5:59 ` Duy Nguyen
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=20160317214355.GA32317@serenity.lan \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=sbeller@google.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).