git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] Extended SHA1 -- "rev^#" syntax to mean "all parents"
Date: Sat, 29 Apr 2006 09:59:53 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0604290954370.3701@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0604291737390.25093@wbgn013.biozentrum.uni-wuerzburg.de>



On Sat, 29 Apr 2006, Johannes Schindelin wrote:
> 
> > A short-hand "rev^#" is understood to be "all parents of the
> > named commit" with this patch.
> 
> Just my 2/100: Why not "rev^*"? I could remember that more easily.

Yeah, that (or ^@ - to match shell "$1" "$2" .. "$@") was my reaction too.

The "rev^#" thing should to my mind return the _number_ of parents, the 
same way "$#" does in shell. I actually pronounce that '#' character 
mentally as "number", but maybe that's just because I'm totally mentally 
damaged by shell programming, and everybody else probably calls it "hash" 
(and some people apparently call it "pound", for some really sick reason).

So "rev^#" literally reads as "revision parent number" to me. Useful? 
Maybe. Maybe not.

		Linus

      reply	other threads:[~2006-04-29 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-29  7:19 [PATCH] built-in diff Junio C Hamano
2006-04-29  9:29 ` [PATCH] built-in diff: assorted updates Junio C Hamano
2006-04-29  9:45 ` [PATCH/RFC] Extended SHA1 -- "rev^#" syntax to mean "all parents" Junio C Hamano
2006-04-29 15:38   ` Johannes Schindelin
2006-04-29 16:59     ` Linus Torvalds [this message]

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=Pine.LNX.4.64.0604290954370.3701@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).