Re: Creating remote branch called HEAD corrupts remote clones
- From
- Stephen Kelly <steveire@gmail.com>
- Date
- Feb 20, 2011, 13:17 UTC
- Message-ID
- <AANLkTinRcmevXz3zV0wtxd7+Q3F4zcH2AZOQk1XVxYXa@mail.gmail.com>
- In-Reply-To
- <AANLkTikmbWkpjioARZrmySpLM8t7kqCX0v1+NKibk_ar@mail.gmail.com>
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@gmail.com> wrote:
Show 20 quoted lines
> On Fri, Jan 21, 2011 at 7:37 PM, Junio C Hamano <gitster@pobox.com> wrote: >> Felipe Contreras <felipe.contreras@gmail.com> 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 >