On Tue, May 7, 2013 at 3:29 AM, Junio C Hamano gits...@pobox.com wrote:
Johan Herland jo...@herland.net writes:
+test_expect_success 'work-around clone with namespaced remote refs' '
+ rm -rf client
+ git init client
+ (
+ cd client
+ git remote add
Johan Herland jo...@herland.net writes:
That said, I could have a go at using refs/peers/* instead of
refs/remotes/*, and see how that works out.
Hmm, I had refs/track/ in mind. Perhaps peers may work as well.
If it sticks, how pervasive do we want this renaming to be? I guess we
don't
Johan Herland jo...@herland.net writes:
+test_expect_success 'work-around clone with namespaced remote refs' '
+ rm -rf client
+ git init client
+ (
+ cd client
+ git remote add origin ../server
+ git config --unset-all
Some users are interested in fetching remote refs into a separate namespace
in the local repo. E.g. instead of the usual remote config:
[remote origin]
fetch = +refs/heads/*:refs/remotes/origin/*
url = ...
they want to keep remote tags separate from local tags, and they may
4 matches
Mail list logo
