From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Evan Driscoll <driscoll@cs.wisc.edu>
Cc: git@vger.kernel.org
Subject: Re: Splitting up a repository
Date: Sat, 4 Dec 2010 14:41:45 +0700	[thread overview]
Message-ID: <AANLkTinLFZTFgov9RtNTFS36BV0xyTm6=kpDE3VZFcEG@mail.gmail.com> (raw)
In-Reply-To: <4CF9EA60.7040402@cs.wisc.edu>
On Sat, Dec 4, 2010 at 2:14 PM, Evan Driscoll <driscoll@cs.wisc.edu> wrote:
> On 12/4/2010 1:09, Nguyen Thai Ngoc Duy wrote:
>> On Sat, Dec 4, 2010 at 12:27 PM, Evan Driscoll <driscoll@cs.wisc.edu> wrote:
>>> Say I have a repo where there are directories repo/foo, repo/bar,
>>> repo/baz. 'foo', 'bar', and 'baz' are loosely related -- closely enough
>>> that I put them together initially, but loosely enough that I now wish I
>>> could check out just 'repo/foo'. Since Git doesn't support partial
>>> checkouts (a bit annoying!),
>>
>> Um.. it does support partial checkouts (check out man page of
>> git-read-tree, sparse checkout section). But you must do a full clone
>> (i.e. your repository will have bar and baz, even if you only checkout
>> foo).
>
> That's sort of spiffy, and I did not know about that. So again, thanks.
>
> That said, I did a bit of reading around, and I'm not sure it does what
> I need.
> http://stackoverflow.com/questions/2336580/sparse-checkout-in-git-1-7-0
> is basically what I want, and the answers seem to indicate it isn't
> possible. (In other words, in my example, when I want a checkout of
> repo/foo, the .git directory needs to be a sibling of foo's contents,
> not a sibling of foo.)
If you want different layout too, then no it does not do that.
Splitting repo is probably best.
-- 
Duy
     prev parent reply	other threads:[~2010-12-04  7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04  5:27 Splitting up a repository Evan Driscoll
2010-12-04  5:33 ` Jeff King
2010-12-04  6:19   ` Evan Driscoll
2010-12-04  7:09 ` Nguyen Thai Ngoc Duy
2010-12-04  7:14   ` Evan Driscoll
2010-12-04  7:41     ` Nguyen Thai Ngoc Duy [this message]
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='AANLkTinLFZTFgov9RtNTFS36BV0xyTm6=kpDE3VZFcEG@mail.gmail.com' \
    --to=pclouds@gmail.com \
    --cc=driscoll@cs.wisc.edu \
    --cc=git@vger.kernel.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.
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).