| commit | 96f12b54f7b2067d668a1ea578a1fc3773e31148 | |
| author | Alex Riesen <raa.lkml@gmail.com> | |
| Fri, 11 May 2007 20:35:22 +0000 (11 22:35 +0200) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Sat, 12 May 2007 16:36:06 +0000 (12 09:36 -0700) | ||
| tree | 2001d27cd065551bf4c163f9da79f0334e7e0a8a | treesnapshot (tar.gz zip) |
| parent | a6e3768f641c2703266422aa05c05f1d01e886b2 | commitdiff |
Allow fetching references from any namespace
not only from the three defined: heads, tags and remotes.
Noticed when I tried to fetch the references created by git-p4-import.bat:
they are placed into separate namespace (refs/p4import/, to avoid showing
them in git-branch output). As canon_refs_list_for_fetch always prepended
refs/heads/ it was impossible, and annoying: it worked before. Normally,
the p4import references are useless anywhere but in the directory managed
by perforce, but in this special case the cloned directory was supposed
to be a backup, including the p4import branch: it keeps information about
where the imported perforce state came from.
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
not only from the three defined: heads, tags and remotes.
Noticed when I tried to fetch the references created by git-p4-import.bat:
they are placed into separate namespace (refs/p4import/, to avoid showing
them in git-branch output). As canon_refs_list_for_fetch always prepended
refs/heads/ it was impossible, and annoying: it worked before. Normally,
the p4import references are useless anywhere but in the directory managed
by perforce, but in this special case the cloned directory was supposed
to be a backup, including the p4import branch: it keeps information about
where the imported perforce state came from.
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| git-parse-remote.sh | diffblobblamehistory |