From: John Szakmeister <john@szakmeister.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [Annoyance] "git log .." thinks ".." is ambiguous
Date: Tue, 3 May 2011 04:38:52 -0400 [thread overview]
Message-ID: <BANLkTimZTV5bf2fNdeu4nEJkkJAdUSwupg@mail.gmail.com> (raw)
In-Reply-To: <7vr58glxro.fsf@alter.siamese.dyndns.org>
On Mon, May 2, 2011 at 3:15 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Either end of revision range operator can be omitted to default to
> HEAD, as in "origin.." (what did I do since I forked) or "..origin" (what
> did they do since I forked). But this resulted in ".." to be interpreted
> as an empty range "HEAD..HEAD", and worse yet, because ".." does exist on
> the filesystem, we get this annoying output:
>
> $ cd Documentation/howto
> $ git log .. ;# give me recent commits that touch Documentation/ area.
> fatal: ambiguous argument '..': both revision and filename
> Use '--' to separate filenames from revisions
Perhaps it's because I still don't use git quite enough yet... but I
don't find the above annoying. *shrug*
-John
prev parent reply other threads:[~2011-05-03 8:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 19:15 [Annoyance] "git log .." thinks ".." is ambiguous Junio C Hamano
2011-05-02 19:33 ` Jeff King
2011-05-02 19:36 ` Jeff King
2011-05-02 20:36 ` Junio C Hamano
2011-05-02 20:42 ` Jeff King
2011-05-02 20:56 ` [PATCH v2] specifying ranges: we did not mean to make ".." an empty set Junio C Hamano
2011-05-02 21:01 ` Jeff King
2011-05-02 21:48 ` Junio C Hamano
2011-05-03 6:39 ` Michael J Gruber
2011-05-03 17:38 ` Junio C Hamano
2011-05-04 6:55 ` Michael J Gruber
2011-05-04 15:36 ` Junio C Hamano
2011-05-04 18:00 ` Junio C Hamano
2011-05-03 1:57 ` [Annoyance] "git log .." thinks ".." is ambiguous Joshua Juran
2011-05-03 6:33 ` Michael J Gruber
2011-05-03 8:17 ` Joshua Juran
2011-05-03 8:45 ` Michael J Gruber
2011-05-03 19:00 ` Junio C Hamano
2011-05-03 8:38 ` John Szakmeister [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=BANLkTimZTV5bf2fNdeu4nEJkkJAdUSwupg@mail.gmail.com \
--to=john@szakmeister.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).