From: Rogan Dawes <discard@dawes.za.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>,
Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog
Date: Fri, 02 Feb 2007 17:15:39 +0200 [thread overview]
Message-ID: <45C3559B.80104@dawes.za.net> (raw)
In-Reply-To: <200702021308.48599.andyparkins@gmail.com>
Andy Parkins wrote:
> 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
next prev parent reply other threads:[~2007-02-02 15:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 17:33 [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog Nicolas Pitre
2007-02-01 19:13 ` Shawn O. Pearce
2007-02-01 20:58 ` Junio C Hamano
2007-02-01 21:29 ` Simon 'corecode' Schubert
2007-02-01 22:12 ` Nicolas Pitre
2007-02-01 22:17 ` Matthias Lederhofer
2007-02-01 22:29 ` [PATCH 4/3] provide a nice @{...} syntax to always mean the " Nicolas Pitre
2007-02-01 23:07 ` [PATCH 5/3], was " Johannes Schindelin
2007-02-01 23:21 ` [PATCH 6/3], was " Johannes Schindelin
2007-02-02 1:15 ` Junio C Hamano
2007-02-01 21:46 ` [PATCH 3/3] prevent HEAD reflog to be interpreted as " Nicolas Pitre
2007-02-02 10:31 ` Jakub Narebski
2007-02-02 10:42 ` Johannes Schindelin
2007-02-02 11:02 ` Lars Hjemli
2007-02-02 13:02 ` Andy Parkins
2007-02-02 14:55 ` Nicolas Pitre
2007-02-02 15:13 ` Nicolas Pitre
2007-02-02 16:11 ` Andy Parkins
2007-02-02 16:35 ` Simon 'corecode' Schubert
2007-02-02 17:19 ` Nicolas Pitre
2007-02-03 17:07 ` Mark Wooding
2007-02-03 17:54 ` Andy Parkins
2007-02-02 13:21 ` Jakub Narebski
2007-02-02 13:47 ` Simon 'corecode' Schubert
2007-02-02 19:40 ` Simon 'corecode' Schubert
2007-02-02 14:52 ` Nicolas Pitre
2007-02-02 15:39 ` Lars Hjemli
2007-02-05 11:11 ` Johannes Schindelin
2007-02-05 11:21 ` Shawn O. Pearce
2007-02-05 12:43 ` Johannes Schindelin
2007-02-05 23:11 ` Lars Hjemli
2007-02-02 13:08 ` Andy Parkins
2007-02-02 15:15 ` Rogan Dawes [this message]
2007-02-02 16:13 ` Andy Parkins
2007-02-03 3:04 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45C3559B.80104@dawes.za.net \
--to=discard@dawes.za.net \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).