From: John Szakmeister <john@szakmeister.net>
Date: Tue, 03 May 2011 08:38:52 GMT
Subject: Re: [Annoyance] "git log .." thinks ".." is ambiguous
Message-ID: <BANLkTimZTV5bf2fNdeu4nEJkkJAdUSwupg@mail.gmail.com>
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