Thread (28 messages) flat view 28 messages, 10 authors, 2016-06-15

Re: [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog

From: Lars Hjemli <hidden>
Date: 2016-06-15 22:42:52

Possibly related (same subject, not in this thread)

On 2/2/07, Nicolas Pitre [off-list ref] wrote:
On Fri, 2 Feb 2007, Lars Hjemli wrote:
quoted
On 2/2/07, Johannes Schindelin [off-list ref] wrote:
quoted
Hi,

On Fri, 2 Feb 2007, Jakub Narebski wrote:
quoted
Perhaps we should use @{...} to refer to reflog for HEAD, or use yet
another special notation?
No.

IMHO "bla@{yesterday}" should give you what "bla" pointed to, yesterday.
In that sense, the proposed reflog on "HEAD" makes perfect sense.
Since HEAD is a synonym for "current branch" everywhere else in git,
while .git/logs/HEAD will be a log of detached HEAD (plus branch
switches, I guess), I think the following makes perfect sense:

 "HEAD@{yesterday}" = current branch, yesterday
 "@{yesterday}"     = detached head (no branch), yesterday
No it doesn't.

HEAD is a moving pointer.  Sometimes it means the current branch,
sometimes it doesn't.

So HEAD is _NOT_ a synonym for "current branch" everywhere already.
All true. I guess I'm just used to thinking about HEAD as a pointer to
the current branch, and that was the reasoning behind my proposal.

But with a detached HEAD this is no longer true, and you end up being right :)

Sorry for the noise

--
larsh
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help