On Mon, May 02, 2011 at 01:56:51PM -0700, Junio C Hamano 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 the current parser interprets ".." 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
>
> Surely we could say "git log ../" or even "git log -- .." to disambiguate,
> but we shouldn't have to.
>
> Helped-by: Jeff King <peff@xxxxxxxx>
> Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx>
Looks good to me.
Doing "..." is still allowed, but will never produce any useful results.
I don't know if it is worth disallowing it to catch errors. I am tempted
to say it should be magic for "@{u}...HEAD", but I think just "..." is
getting unreadably magical. "@{u}...HEAD" is already pretty concise and
is much more readable.
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html