Re: Wishlist for a bundle-only transport mode

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Nov 21, 2007, 15:59 UTC
Message-ID: <Pine.LNX.4.64.0711211554370.27959@racer.site>
In-Reply-To: <8aa486160711210654p357ccd87i4809e0cda9471303@mail.gmail.com>

Hi,

On Wed, 21 Nov 2007, Santi B?jar wrote:

> 1) git-clone does not accept a bundle file, even if git-fetch does. I've 
> made a patch to use git-fetch in git-clone for this.

This, along with rewriting git-clone as a very thin wrapper over git-init, -remote and -fetch, is a really low hanging fruit.

Or maybe go the full nine yards and build it in. Should be a breeze now, given parse_options() and run_command().

> 2) The bundles created with "git bundle" does not record the HEAD, they 
> resolve the symbolic name to a branch name.

It imitates ls-remote output.

Show 11 quoted lines

> 3) I can "git fetch" a bundle but I cannot "git push" a bundle, so if I have:
> 
> [remote "bundle"]
>   url = /file/to/bundle
>   fetch = "+refs/heads/*:refs/remotes/bundle/*"
> 
> $ git push bundle
> 
> would create a bundle in /file/to/bundle with the same branches as a
> normal git push, but considering the remote branches as the local
> remotes/bundle/*

Does not seem to be too complicated to add it to transport.c IMHO. Something similar to rsync_transport_push(). And I'd definitely refuse to overwrite any existing file.

Ciao, Dscho