Cloning a remote tag without using git-fetch-pack directly?
Using fetch-pack, I can clone a single tag from a repository:
/tmp/testrepo$ git init
Initialized empty Git repository in /tmp/testrepo/.git/ /tmp/testrepo$ git fetch-pack /home/josh/src/linux-2.6/.git refs/tags/v2.6.12
remote: Counting objects: 31617, done.
remote: Compressing objects: 100% (21083/21083), done.
Receiving objects: 100% (31617/31617), 52.56 MiB | 5.27 MiB/s, done.
remote: Total 31617 (delta 12862), reused 19495 (delta 10331) Resolving deltas: 100% (12862/12862), done.
keep c80bd1def293bc11591159c96970d8becfe3b2d926791a8bcf0e6d33f43aef7682bdb555236d56de refs/tags/v2.6.12 /tmp/testrepo$ git show 26791a8bcf0e6d33f43aef7682bdb555236d56de | head -20 tag v2.6.12
This is the final 2.6.12 release
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQBCsykyF3YsRnbiHLsRAvPNAJ482tCZwuxp/bJRz7Q98MHlN83TpACdHr37 o6X/3T+vm8K3bf3driRr34c=
=sBHn
-----END PGP SIGNATURE-----
commit 9ee1c939d1cb936b1f98e8d81aeffab57bae46ab
Author: Linus Torvalds <[email protected]> Date: Fri Jun 17 12:48:29 2005 -0700
Linux 2.6.12
Makefile +0 -0
--- a/Makefile
However, I can't seem to find any way to convince git clone to do the same thing for me. git clone will clone a branch, but not a tag.
/tmp/testrepo$ git clone /home/josh/src/linux-2.6/.git -b refs/tags/v2.6.12 Cloning into linux-2.6...
done.
warning: Remote branch refs/tags/v2.6.12 not found in upstream origin, using HEAD instead
On a different note, git fetch-pack seems to silently fail if asked to fetch a remote tag which points at a tree object rather than a commit object:
/tmp/testrepo$ git init
Initialized empty Git repository in /tmp/testrepo/.git/ /tmp/testrepo$ git fetch-pack /home/josh/src/linux-2.6/.git refs/tags/v2.6.12-tree
(1) /tmp/testrepo$ echo $?
1
I realize that I want to do something strange here, but it seems like a kind of strange that git already supports in at least some ways, just not in others. Am I missing something?
Thanks,
Josh Triplett
Quoted 5 lines · Josh Triplett
Using fetch-pack, I can clone a single tag from a repository:
/tmp/testrepo$git init
Initialized empty Git repository in/tmp/testrepo/.git//tmp/testrepo$git fetch-pack/home/josh/src/linux-2.6/.gitrefs/tags/v2.6.12
I don't think there is any reason to use fetch-pack here instead of fetch. The latter will handle other non-git protocols like dumb http and git-over-http.
Quoted 7 lines
However, I can't seem to find any way to convince git clone to do the same thing for me. git clone will clone a branch, but not a tag.
/tmp/testrepo$git clone/home/josh/src/linux-2.6/.git-b refs/tags/v2.6.12 Cloning into linux-2.6...
done.
warning: Remote branch refs/tags/v2.6.12 not found in upstream origin, using HEAD instead
Right. There is no way to do what you want with clone. The "-b" option is not "just clone this one thing", it is "clone everything, but the branch I am interested in is ...". The fetch refspec remains "+refs/heads/*:refs/remotes/origin/*".
To clone a subset of a repository, you have to do the init+fetch trick, as you did above. If you want the configuration set up by clone, you can do that, too, with "git config". So the equivalent commands to the clone you want are:
git init linux-2.6
cd linux-2.6
git config remote.origin.url /home/josh/src/linux-2.6 git config remote.origin.fetch refs/tags/v2.6.12 git fetch origin
We could make clone more flexible with respect to such things, but I don't know how useful that would be. A very small minority of power users want to use weird fetch refspecs, and it is simple enough to configure them manually, as above.
Quoted 9 lines
On a different note, git fetch-pack seems to silently fail if asked to fetch a remote tag which points at a tree object rather than a commit object:
/tmp/testrepo$git init
Initialized empty Git repository in/tmp/testrepo/.git//tmp/testrepo$git fetch-pack/home/josh/src/linux-2.6/.gitrefs/tags/v2.6.12-tree
(1)/tmp/testrepo$echo $?
1
Did you mean v2.6.11-tree? There is no v2.6.12-tree in standard linux-2.6 repositories. So fetch-pack is failing because there are no matching refs to fetch. This works for me:
$ git init $ git fetch-pack /home/peff/compile/linux-2.6 refs/tags/v2.6.11-tree remote: Counting objects... ...
If you want better error messages, use the fetch porcelain:
$ git init $ git fetch /home/peff/compile/linux-2.6 refs/tags/v2.6.12-tree fatal: Couldn't find remote ref refs/tags/v2.6.12-tree fatal: The remote end hung up unexpectedly
-Peff
Quoted 20 lines · Jeff King
Quoted 5 lines · Josh Triplett
Using fetch-pack, I can clone a single tag from a repository:
/tmp/testrepo$git init
Initialized empty Git repository in/tmp/testrepo/.git//tmp/testrepo$git fetch-pack/home/josh/src/linux-2.6/.gitrefs/tags/v2.6.12I don't think there is any reason to use fetch-pack here instead of fetch. The latter will handle other non-git protocols like dumb http and git-over-http.
Quoted 7 lines
However, I can't seem to find any way to convince git clone to do the same thing for me. git clone will clone a branch, but not a tag.
/tmp/testrepo$git clone/home/josh/src/linux-2.6/.git-b refs/tags/v2.6.12 Cloning into linux-2.6...
done.
warning: Remote branch refs/tags/v2.6.12 not found in upstream origin, using HEAD instead
Quoted 4 lines
Right. There is no way to do what you want with clone. The "-b" option is not "just clone this one thing", it is "clone everything, but the branch I am interested in is ...". The fetch refspec remains "+refs/heads/*:refs/remotes/origin/*".
Oh, good to know; I hadn't yet figured out that -b didn't change the refspec.
Quoted 11 lines
To clone a subset of a repository, you have to do the init+fetch trick, as you did above. If you want the configuration set up by clone, you can do that, too, with "git config". So the equivalent commands to the clone you want are:
git init linux-2.6
cd linux-2.6
git config remote.origin.url/home/josh/src/linux-2.6git config remote.origin.fetch refs/tags/v2.6.12 git fetch origin
Quoted 4 lines
We could make clone more flexible with respect to such things, but I don't know how useful that would be. A very small minority of power users want to use weird fetch refspecs, and it is simple enough to configure them manually, as above.
I'd certainly appreciate having a "git clone --refspec=..." or similar, but thanks for suggesting fetch rather than fetch-pack! I actually don't always want the remote set up for this particular purpose, so using fetch works out well.
Quoted 19 lines
Quoted 9 lines
On a different note, git fetch-pack seems to silently fail if asked to fetch a remote tag which points at a tree object rather than a commit object:
/tmp/testrepo$git init
Initialized empty Git repository in/tmp/testrepo/.git//tmp/testrepo$git fetch-pack/home/josh/src/linux-2.6/.gitrefs/tags/v2.6.12-tree
(1)/tmp/testrepo$echo $?
1Did you mean v2.6.11-tree? There is no v2.6.12-tree in standard linux-2.6 repositories. So fetch-pack is failing because there are no matching refs to fetch. This works for me:
$ git init $ git fetch-pack /home/peff/compile/linux-2.6 refs/tags/v2.6.11-tree remote: Counting objects... ...
Quoted 6 lines
If you want better error messages, use the fetch porcelain:
$ git init $ git fetch /home/peff/compile/linux-2.6 refs/tags/v2.6.12-tree fatal: Couldn't find remote ref refs/tags/v2.6.12-tree fatal: The remote end hung up unexpectedly
Well, *that's* embarassing. I thought I'd tested that with a couple of other repositories and tree-tag objects, but apparently not.
Sadly, though, I still can't check out the result:
/tmp/linux-2.6$ git checkout FETCH_HEAD
fatal: Cannot switch branch to a non-commit.
(128) /tmp/linux-2.6$ git checkout -b master FETCH_HEAD
fatal: Cannot switch branch to a non-commit.
I guess I'd hoped for something similar to "detached HEAD" mode.
Based on this, I need still to switch to using faked commits rather than trees.
- Josh Triplett
Quoted 8 lines · Josh Triplett
Sadly, though, I still can't check out the result:
/tmp/linux-2.6$git checkoutFETCH_HEAD
fatal: Cannot switch branch to a non-commit.
(128)/tmp/linux-2.6$git checkout -b masterFETCH_HEAD
fatal: Cannot switch branch to a non-commit.I guess I'd hoped for something similar to "detached HEAD" mode.
No, it wouldn't make any sense to have a non-commit in HEAD, detached or otherwise, since you couldn't build commits on top of it (what would the new commit's parent pointer have in it?).
If you just want to check the files out into the working tree, you can do:
git read-tree --reset -u FETCH_HEAD
But I'm not really clear on what you're trying to accomplish with all of this. If you can describe your ultimate goal, I might be able to help more.
-Peff
Hi,
Some quick additional thoughts.
Quoted 10 lines · Jeff King
To clone a subset of a repository, you have to do the init+fetch trick, as you did above. If you want the configuration set up by clone, you can do that, too, with "git config". So the equivalent commands to the clone you want are:
git init linux-2.6
cd linux-2.6
git config remote.origin.url/home/josh/src/linux-2.6git config remote.origin.fetch refs/tags/v2.6.12 git fetch origin
Someone fetching v2.6.12 to build on it today is probably not planning to run "git fetch origin" to fetch the same tag tomorrow. So
git init linux-2.6
cd linux-2.6
git remote add origin ~/src/linux-2.6
git fetch origin refs/tags/v2.6.12
or even "...; git fetch ~/src/linux-2.6 refs/tags/v2.6.12" could be closer to what is needed.
If for some reason you do want to track how the remote v2.6.12 tag evolves, "git remote" has a funny way to do that:
git remote add --mirror=fetch -ttags/v2.6.12 origin ~/src/linux.2.6
The documentation calls the argument to -t "<branch>", but in mirror mode it is actually a refspec relative to refs/.
With luck (depending on what you are looking to do), git-new-workdir[1] or "git archive --remote" could also be helpful.
Regards,
Jonathan
[1] with the usual avoidable caveats described at
https://git.wiki.kernel.org/index.php/SoC2011Ideas#Multiple_work_trees