On Nov 21, 2007 5:36 PM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi, > > On Wed, 21 Nov 2007, Santi B?jar wrote: > > > On Nov 21, 2007 4:59 PM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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. I did not say it was difficult, I said it was not a very thin wrapper. > > > > > 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. Maybe because of my non-native english :-) > I thought you were expecting that the first line > would read > > refs/heads/master HEAD or ref: refs/heads/master HEAD That would be perfect, but it is a different story. > > 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. Thank you. Santi - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html