git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Peter Foley <pefoley2@verizon.net>
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: Sun, 19 Jun 2011 21:21:42 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1106192111250.18284@linux.foleyremote.com> (raw)
In-Reply-To: <BANLkTimjixOT=j9Xf=Ti-04cRw2noC0NiQ@mail.gmail.com>



On Sun, 19 Jun 2011, Shawn Pearce 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? What problem does this address? Is that worth the pain
> this puts on every other in-flight change that is still being
> developed, or is already in the review pipeline?
> 
> -- 
> Shawn.
> 

The basic idea is to organize the git source directory more than it is 
right now (a flat directory with all the source files at the toplevel).
Moving the contents of libgit.a seemed to be a logical way to start.
 
Thanks,

Peter

  reply	other threads:[~2011-06-20  1:23 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 [this message]
2011-06-20  5:59   ` Junio C Hamano
2011-06-20  6:47     ` Jonathan Nieder
2011-06-20 14:55   ` Thiago Farina
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=alpine.LNX.2.00.1106192111250.18284@linux.foleyremote.com \
    --to=pefoley2@verizon.net \
    --cc=git@vger.kernel.org \
    --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).