Junio C Hamano wrote: > * Subsequent fetch, when the glob is not '+' variant, would > download the config from the remote in order to see which are > marked as "rewinds", and ignores the branches that are marked > as such. > > I am a bit unhappy that subsequent fetches have to re-read the > remote config every time. I can sort-of-see we can cram the > "this is expected to be rewound" information as part of > peek-remote exchange to avoid the overhead, but I do not think > it is easily doable for dumb transports without breaking the > backward compatibility. Perhaps below the "Pull: refs/heads/*:refs/remotes/origin/*" (or config equivalent) we should list (in some format) branches which are not to be fetched becaus they don't fast forward. One option, namely Pull:-refs/heads/pu:refs/remotes/origin/pu (or config equivalent)comes to mind. It has the advantage that when we decide to fetch this branch, it would be as easy as changing '-' to '+'. Or we can use '!' instead of '-' if you think it is more readable (probably is). -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - 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