Re: [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog
- From
- Rogan Dawes <discard@dawes.za.net>
- Date
- Feb 2, 2007, 15:15 UTC
- Message-ID
- <45C3559B.80104@dawes.za.net>
- In-Reply-To
- <200702021308.48599.andyparkins@gmail.com>
Andy Parkins wrote:
Show 19 quoted lines
> On Thursday 2007 February 01 17:33, Nicolas Pitre wrote:
>
>> The work in progress to enable separate reflog for HEAD will make it
>> independent from reflog of any branch HEAD might be pointing to. In
>> the mean time disallow HEAD@{...} until that work is completed. Otherwise
>> people might get used to the current behavior which makes HEAD@{...} an
>> alias for <current_branch>@{...} which won't be the case later.
>
> I hadn't really appreciated the implications of all this HEAD reflog stuff
> until now.
>
> Please, please, HEAD@{} should /always/ be an alias for <current_branch>@{}.
>
> There is one special case: when head is detached, <current_branch> would then
> be the "unnamed branch" for reflog purposes; personally I'd like that stored
> in .git/logs/DETACHED_HEAD or similar - in particular not in .git/logs/HEAD.
>
> Andy
> However, if HEAD@{} means what was HEAD pointing at at the indicated time, and @{} means "current branch", then we need no exceptions, and the common case is shorter.
Rogan