From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>, Thomas Rast <trast@inf.ethz.ch>
Subject: Re: [PATCH 4/5] git-log.txt: rewrite note on why "--" may be required
Date: Sun, 21 Apr 2013 13:08:00 +0530 [thread overview]
Message-ID: <CALkWK0kiT7vggXgqGs2iiMooiw7TyJEgr2=Yy06S7H1NKiWJ3g@mail.gmail.com> (raw)
In-Reply-To: <7v8v4cwd6g.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> A list of revisions is merely a way to specify "revision range" that
> are reachable from any of these revisions listed. "log A B" won't
> stop by just showing A and B (that would be "show A B"), but will
> list those that are reachable from A B, so in the context of
> discussing the arguments given to "git log" command, "A B" is still
> "revision range".
... and what about 'git log HEAD^!'? Is that a range? What about
'git log HEAD:README' (hint: it doesn't error out)? I would argue that
"A B" is not inherently a revision range, but rather two revisions.
It's upto different commands to interpret it differently.
Then again, in the context of log, we just want ranges (also
considering we had <since>..<until> for this long, and I didn't even
object to it). So I'll go with your "revision range", but I won't
claim that it's technically accurate.
next prev parent reply other threads:[~2013-04-21 7:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 11:45 [PATCH 0/5] Documentation/shortlog improvements Ramkumar Ramachandra
2013-04-20 11:45 ` [PATCH 1/5] git-shortlog.txt: remove (-h|--help) from OPTIONS Ramkumar Ramachandra
2013-04-20 11:45 ` [PATCH 2/5] builtin/shortlog.c: make usage string consistent with log Ramkumar Ramachandra
2013-04-20 11:45 ` [PATCH 3/5] git-log.txt: fix description of <since>..<until> Ramkumar Ramachandra
2013-04-20 22:25 ` Jonathan Nieder
2013-04-21 7:18 ` Ramkumar Ramachandra
2013-04-21 7:41 ` Jonathan Nieder
[not found] ` <CAPc5daVcovqrHP-YWnkcQWwev5TW5S8ioX-bWyAnNG2PTg_XMw@mail.gmail.com>
2013-04-21 8:17 ` [PATCH/RFC] glossary: a revision is just a commit Jonathan Nieder
2013-04-21 19:00 ` Junio C Hamano
2013-04-21 7:19 ` [PATCH 3/5] git-log.txt: fix description of <since>..<until> Junio C Hamano
2013-04-21 6:40 ` Junio C Hamano
2013-04-20 11:45 ` [PATCH 4/5] git-log.txt: rewrite note on why "--" may be required Ramkumar Ramachandra
2013-04-21 6:51 ` Junio C Hamano
2013-04-21 7:26 ` Ramkumar Ramachandra
2013-04-21 7:33 ` Junio C Hamano
2013-04-21 7:38 ` Ramkumar Ramachandra [this message]
2013-04-21 7:46 ` Junio C Hamano
2013-04-21 8:00 ` Ramkumar Ramachandra
2013-04-21 8:09 ` Jonathan Nieder
2013-04-21 8:15 ` Ramkumar Ramachandra
2013-04-21 8:17 ` Jonathan Nieder
2013-04-21 8:33 ` Junio C Hamano
2013-04-21 9:05 ` Ramkumar Ramachandra
2013-04-21 9:46 ` Ramkumar Ramachandra
2013-04-21 10:09 ` Jonathan Nieder
[not found] ` <CAPc5daV39HsoRR2pj34Tz1kQKFVRrp+NZpMM2BremocqvToA+A@mail.gmail.com>
2013-04-21 8:13 ` Ramkumar Ramachandra
2013-04-21 8:23 ` Ramkumar Ramachandra
2013-04-21 7:39 ` Junio C Hamano
2013-04-21 7:57 ` Ramkumar Ramachandra
2013-04-22 2:40 ` Junio C Hamano
2013-04-22 9:36 ` Thomas Rast
2013-04-22 9:40 ` Thomas Rast
2013-04-22 14:55 ` Junio C Hamano
2013-04-20 11:45 ` [PATCH 5/5] git-shortlog.txt: make SYNOPSIS match log, update OPTIONS Ramkumar Ramachandra
2013-04-21 7: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='CALkWK0kiT7vggXgqGs2iiMooiw7TyJEgr2=Yy06S7H1NKiWJ3g@mail.gmail.com' \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@inf.ethz.ch \
/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).