From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Wishlist for a bundle-only transport mode
Date: Wed, 21 Nov 2007 16:36:33 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711211632090.27959@racer.site> (raw)
In-Reply-To: <8aa486160711210815g5a1973c2see28a6263fc56030@mail.gmail.com>
Hi,
On Wed, 21 Nov 2007, Santi B?jar wrote:
> On Nov 21, 2007 4:59 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> > 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.
>
> For the basic/normal mode it can be a very thin wrapper but you have to
> support --local, --shared, --reference...
That is not all that difficult.
> > > 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.
>
> No, it does not.
>
> With a newly created project with one commit:
>
> $ git ls-remote git.git
> b71992713c17c3a29f9566e1b50e8cf402375faf HEAD
> b71992713c17c3a29f9566e1b50e8cf402375faf refs/heads/master
>
> $ git bundle create git.bdl HEAD master
>
> $ git bundle list-heads git.bdl
> b71992713c17c3a29f9566e1b50e8cf402375faf refs/heads/master
> b71992713c17c3a29f9566e1b50e8cf402375faf refs/heads/master
Ah, I misunderstood. I thought you were expecting that the first line
would read
refs/heads/master HEAD
Alas, this behaviour stems from dwim_ref() returning "refs/heads/master"
as real ref.
I am not quite sure how to solve this, though. Let me see what I can come
up with.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-21 16:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 14:54 Wishlist for a bundle-only transport mode Santi Béjar
2007-11-21 15:04 ` Jakub Narebski
2007-11-21 15:24 ` Santi Béjar
2007-11-21 15:46 ` Johannes Schindelin
2007-11-21 16:52 ` Jakub Narebski
2007-11-21 16:59 ` Johannes Schindelin
2007-11-21 17:11 ` Jakub Narebski
2007-11-21 17:26 ` Johannes Schindelin
2007-11-21 17:52 ` Jakub Narebski
2007-11-22 9:42 ` Santi Béjar
2007-11-22 10:02 ` Junio C Hamano
2007-11-23 9:18 ` Jakub Narebski
2007-11-23 9:31 ` Junio C Hamano
2007-11-23 10:04 ` Jakub Narebski
2007-11-23 10:13 ` Santi Béjar
2007-11-23 12:18 ` Johannes Schindelin
2007-11-23 15:06 ` Junio C Hamano
2007-11-23 15:34 ` Santi Béjar
2007-11-23 16:05 ` Junio C Hamano
2007-11-23 16:39 ` Santi Béjar
2007-11-24 19:15 ` Junio C Hamano
2007-11-23 19:09 ` Jakub Narebski
2007-11-21 15:59 ` Johannes Schindelin
2007-11-21 16:15 ` Santi Béjar
2007-11-21 16:36 ` Johannes Schindelin [this message]
2007-11-21 16:44 ` Santi Béjar
2007-11-21 16:53 ` [PATCH] bundle create: keep symbolic refs' names instead of resolving them Johannes Schindelin
2007-11-22 12:03 ` Johannes Schindelin
2007-11-22 12:24 ` [REPLACEMENT PATCH] " Johannes Schindelin
2007-11-21 16:23 ` Wishlist for a bundle-only transport mode Kristian Høgsberg
2007-11-21 17:07 ` Johannes Schindelin
2007-11-21 17:06 ` Jakub Narebski
2007-11-21 17:29 ` Johannes Schindelin
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=Pine.LNX.4.64.0711211632090.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sbejar@gmail.com \
/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).