git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lars Hjemli" <hjemli@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Jakub Narebski" <jnareb@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog
Date: Fri, 2 Feb 2007 16:39:22 +0100	[thread overview]
Message-ID: <8c5c35580702020739v383c1efeu7851f5eb2a2ea5f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702020945090.3021@xanadu.home>

On 2/2/07, Nicolas Pitre <nico@cam.org> wrote:
> On Fri, 2 Feb 2007, Lars Hjemli wrote:
>
> > On 2/2/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > Hi,
> > >
> > > On Fri, 2 Feb 2007, Jakub Narebski wrote:
> > >
> > > > 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

  reply	other threads:[~2007-02-02 15:39 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 [this message]
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
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=8c5c35580702020739v383c1efeu7851f5eb2a2ea5f@mail.gmail.com \
    --to=hjemli@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --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).