From: Alex Riesen <raa.lkml@gmail.com>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] t3502: Disambiguate between file and rev by adding --
Date: Mon, 5 Nov 2007 23:25:30 +0100 [thread overview]
Message-ID: <20071105222530.GA4208@steel.home> (raw)
In-Reply-To: <20071104153126.GA61398@173.242.249.10.in-addr.arpa>
Brian Gernhardt, Sun, Nov 04, 2007 16:31:26 +0100:
> This test failed because git-diff didn't know if it was asking for the
> file "a" or the branch "a". Adding "--" at the end of the ambiguous
> commands allows the test to finish properly.
To be precise: this is ambiguous only on case-challenged filesystems
next prev parent reply other threads:[~2007-11-05 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 15:31 [PATCH] t3502: Disambiguate between file and rev by adding -- Brian Gernhardt
2007-11-05 22:25 ` Alex Riesen [this message]
2007-11-06 1:17 ` Brian Gernhardt
2007-11-06 1:20 ` 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=20071105222530.GA4208@steel.home \
--to=raa.lkml@gmail.com \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).