From: Thiago Farina <tfransosi@gmail.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: Peter Foley <pefoley2@verizon.net>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] Move contents of libgit.a to lib subdirectory
Date: Mon, 20 Jun 2011 11:55:58 -0300 [thread overview]
Message-ID: <BANLkTimo71oftT2h4tXJhX7=zqjZipV3qw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimjixOT=j9Xf=Ti-04cRw2noC0NiQ@mail.gmail.com>
On Sun, Jun 19, 2011 at 10:06 PM, Shawn Pearce <spearce@spearce.org> wrote:
> On Sun, Jun 19, 2011 at 17:50, Peter Foley <pefoley2@verizon.net> wrote:
>> This patch tries to organize the git source tree by moving the files which
>> make up libgit.a to a lib subdirectory.
>> Before this patch the toplevel source directory contained 285 files.
>> After this patch the root directory will contain 167 files and
>> the lib subdirectory will contain 119 files
> ...
>
> Thanks. But why is this amount of churn necessary or being
> recommended?
If that becomes from time to time as Jonathan pointed out, probably it
means that other people thinks the physical layout of the source files
could be improved.
> What problem does this address?
I think it's the big number of source files at the toplevel directory.
next prev parent reply other threads:[~2011-06-20 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 0:50 [PATCH/RFC] Move contents of libgit.a to lib subdirectory Peter Foley
2011-06-20 1:06 ` Shawn Pearce
2011-06-20 1:21 ` Peter Foley
2011-06-20 5:59 ` Junio C Hamano
2011-06-20 6:47 ` Jonathan Nieder
2011-06-20 14:55 ` Thiago Farina [this message]
2011-06-20 1:12 ` Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTimo71oftT2h4tXJhX7=zqjZipV3qw@mail.gmail.com' \
--to=tfransosi@gmail.com \
--cc=git@vger.kernel.org \
--cc=pefoley2@verizon.net \
--cc=spearce@spearce.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).