bump. I don't think this issue was fixed, was it? (no need to put kdepim back in the cc list) On Sat, Jan 22, 2011 at 1:46 PM, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote: > On Fri, Jan 21, 2011 at 7:37 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: >> >>> I don't fully understand the issue, so excuse me if this is totally >>> wrong, but wouldn't a rule like 'you can't create a branch for which >>> there's already a symbolic ref' do the trick? >> >> But whose symbolic ref are you checking against? Your own, or ones in >> somebody else's repository that you haven't recently updated from? > > The local ones. That means that somebody can't create a 'HEAD' branch > locally, and can't push a 'HEAD' branch either, as the remote server > would already have a 'HEAD' symbolic link. And actually, if for some > reason I have a FOO_HEAD, and I fetch a branch called bob/FOO_HEAD, > obviously the local symbolic ref without namespace should take > precedence. > > -- > Felipe Contreras > -- 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