On Thursday 02 November 2017 01:21 PM, Junio C Hamano wrote:
Kaartic Sivaraam writes:
I was able to spare some time to dig into this and found a few things.
First, it seems that the issue is more generic and the BUG kicks in
whenever HEAD is not a symbolic ref.
Interesting.
Let me detail
Kaartic Sivaraam writes:
> I was able to spare some time to dig into this and found a few things.
>
> First, it seems that the issue is more generic and the BUG kicks in
> whenever HEAD is not a symbolic ref.
Interesting.
Shortly we'll be rewinding the tip of 'next', and it is a good
opportun
I was able to spare some time to dig into this and found a few things.
First, it seems that the issue is more generic and the BUG kicks in
whenever HEAD is not a symbolic ref. I noticed that because when HEAD
is a symbolic ref there was a change in the error message shown by git.
In (2.11.0) I get
I just noticed this recently while trying to see if a recent change [1]
that disallowed the possibility of creating HEAD also allowed renaming
branches named "HEAD" that were created using previous versions that
allowed it. Unfortunately (or fortunately (?)), I was in the middle of
an interactive r
4 matches
Mail list logo