Re: git-fetch per-repository speed issues

From: Ryan Anderson <ryan@michonline.com>
Date: Jul 4, 2006, 01:55 UTC
Message-ID: <44A9CAA5.4050602@michonline.com>
In-Reply-To: <20060704014441.GB9061@coredump.intra.peff.net>

Jeff King wrote:

Show 22 quoted lines

> On Mon, Jul 03, 2006 at 06:22:26PM -0700, Ryan Anderson wrote:
>
>   
>> You can have multiple source trees, one per 'branch' (which is a bit of
>> a bad term here), and have completely unrelated things in the branches.
>>
>> See, for an example, the main Git repo, which has the "man", "html", and
>> "todo" branches, logically distinct and (somewhat) unrelated to the main
>> branch tucked away in "master".
>>     
>
> Right, I know, but my complaint is that I can't then turn that into a
> directory hierarchy of .../man, .../html, .../todo that are all checked
> out at the same time (there are obviously ways of playing with it, say
> by setting GIT_DIR and doing a checkout in those directories, but then I
> can't use git in the normal way).
>
> The best I can come up with is having man, html, and todo repos pointing
> to the one (now local) repo which contains everything. But then pushing
> is a two-step process.
>
>

Hrm, if I understand CVS at all, the old workflow was "cvsup a copy of the repository, update a working tree against that", which is, I think, actually even worse than the Git equivalent, since you can't reliably even commit to that local clone of the CVS repository.

What am I missing?

You can still push directly upstream, I suppose, and just do 2-stage pulls down.

-- 
Ryan Anderson
  sometimes Pug Majere