From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Re: Commit-ish shortcut for immediate parent range
Date: Sun, 22 Oct 2006 21:17:45 +0100 [thread overview]
Message-ID: <200610222117.45766.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610221017180.3962@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Sunday 2006, October 22 18:25, Linus Torvalds wrote:
> Umm. That's not actually a very sensible operation. It's only sensible in
> the special case of "diff", and for that special case, what we do is to
> actually just say that the _command_ is special, not the range.
>
> It's called "git show".
You're entirely correct, that that is what I was looking for in that
particular case. However, the reason I raised it as a question was that I
was poking around with git (which I'm enjoying immensely by the way - it
really is as perfect an SCM as I have ever used) and in short succession did
git-diff X^..X
git-log X^..X
git-format-patch X^..X
I imagined that I would eventually stumble on other git commands where I would
want to do this operation again. I'm sure I will have picked an incorrect
command in each case, however, they all did exactly what I wanted so I
stopped looking for the "right" command :-)
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-22 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 14:48 Commit-ish shortcut for immediate parent range Andy Parkins
2006-10-22 15:11 ` Jakub Narebski
2006-10-22 17:25 ` Linus Torvalds
2006-10-22 18:25 ` Linus Torvalds
2006-10-22 20:17 ` Andy Parkins [this message]
2006-10-22 20:56 ` Linus Torvalds
2006-10-22 21:41 ` Jakub Narebski
2006-10-22 22:09 ` Johannes Schindelin
2006-10-22 22:33 ` Jakub Narebski
2006-10-22 23:36 ` Junio C Hamano
2006-10-23 3:33 ` Linus Torvalds
2006-10-22 20:55 ` Johannes Schindelin
2006-10-22 19:53 ` Jeff King
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=200610222117.45766.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).