git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: git@vger.kernel.org
Subject: Re: [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog
Date: Fri, 02 Feb 2007 20:40:02 +0100	[thread overview]
Message-ID: <45C39392.9070000@fs.ei.tum.de> (raw)
In-Reply-To: <45C3410A.4030407@fs.ei.tum.de>

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

Simon 'corecode' Schubert wrote:
> Lars Hjemli wrote:
>>  "HEAD@{yesterday}" = current branch, yesterday
>>  "@{yesterday}"     = detached head (no branch), yesterday
> 
> +1 (actually not only "detached head", but "where my workdir was", 
> including named branches as well)

okay, I take this back and claim the opposite:

+1 for

@{..} = current branch
HEAD@{..} = log of where HEAD was, detached or not detached, no matter

cheers
  simon

-- 
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-02-02 19:40 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 [this message]
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
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=45C39392.9070000@fs.ei.tum.de \
    --to=corecode@fs.ei.tum.de \
    --cc=git@vger.kernel.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).