git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Commit-ish shortcut for immediate parent range
Date: Sun, 22 Oct 2006 23:41:57 +0200	[thread overview]
Message-ID: <ehgoii$1ap$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0610221331571.3962@g5.osdl.org

Linus Torvalds wrote:

> Now, "git show" obviously does exactly what you probably wanted, but for 
> future reference, the "git log" family of commands also take a "number of 
> commits" limiter.
> 
> So you can also do things like
> 
>         git log --cc -1 X
> 
> and it will actually do something very similar to "git show". It's not 
> _quite_ identical, but it's close - at least for the special case of a 
> single commit.

And of course this shortcut is not documented. git-log(1) and
git-rev-list(1) talks only about "--max-count=<n>", and "-n <n>",
and doesn't talk about possible shortcuts "-n<n>" and "-<n>".
Perhaps because those shortcuts are discouraged?

Additionally you can find "-n <n>" shortcut only further on
the git-rev-list(1).


Patch will follow.

BTW. what does "recursive diff" mean (in git)?
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2006-10-22 21:41 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
2006-10-22 20:56     ` Linus Torvalds
2006-10-22 21:41       ` Jakub Narebski [this message]
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='ehgoii$1ap$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --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).