On Fri, 28 Sep 2007, Shawn O. Pearce wrote: > Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > Beats me; Junio, what's your test case? > > If I understood him correctly it is this: > > mkdir foo; cd foo; git init > git config remote.origin.url git://repo.or.cz/alt-git.git > git config remote.origin.fetch refs/heads/master:refs/remotes/origin/master > git config --add remote.origin.fetch refs/heads/maint:refs/remotes/origin/maint > git pull > > We should see "master" listed in .git/FETCH_HEAD as a "for-merge" > and "maint" listed as a "not-for-merge"... > > But if that remote.origin.fetch was a wildcard spec this shouldn't > happen as the results are unpredictable. But above the user > explicitly put master first, so it should be defaulted to. But after that sequence, the right thing does happen. So I'm guessing that he has some different sequence that triggers a bug. -Daniel *This .sig left intentionally blank* - 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
