Hi! On Wed, 3 Jul 2013 09:54:58 -0700, Jason Merrill <[email protected]> wrote: > On 07/03/2013 02:47 AM, Thomas Schwinge wrote: > > OK, that of course works, but from the wiki page I got the idea that it > > explicitly was meant to merge these together. So assuming this used to > > work in the past, I wonder what so that it no longer does; such as Git > > allowing such duplicates merging in the past, and/or was the intersection > > of refs/remotes/* and refs/heads/* meant to be the empty set (then I > > assume the merging would work, too), but no longer is? > > Hmm, it looks like I wrote that up without actually doing it myself, > oops. I'll correct the wiki.
Hmm, seems the change you've done:
fetch = refs/heads/*:refs/remotes/origin/*
fetch = refs/remotes/*:refs/remotes/origin/remotes/*
..., is not ideal either: using »git fetch --verbose --prune« I now see
all the refs being downloaded -- and then immediatelly pruned again. :-/
Would the following be an appropriate variant? Seems to work fine, but
"disturbs" the regular Git refs namespace a bit?
fetch = refs/heads/*:refs/remotes/upstream/*
fetch = refs/remotes/*:refs/remotes/upstream-remotes/*
Grüße,
Thomas
pgp_6ETin3ETl.pgp
Description: PGP signature
