From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] setup.c:verify_non_filename(): don't die unnecessarily while disambiguating
Date: Mon, 6 Aug 2007 04:03:01 -0400 [thread overview]
Message-ID: <20070806080301.GL9527@spearce.org> (raw)
In-Reply-To: <7vk5s9dt2b.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <gitster@pobox.com> wrote:
> If you have a working tree _file_ "foo", attempt to refer to a
> branch "foo/bar" without -- to disambiguate, like this:
>
> $ git log foo/bar
> ---
>
> * This was from a real-life experience Shawn had.
Ack. I have done this many times, and every time I thought I was
going nuts. Until Junio found this bug tonight. Many thanks.
--
Shawn.
prev parent reply other threads:[~2007-08-06 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 7:24 [PATCH] setup.c:verify_non_filename(): don't die unnecessarily while disambiguating Junio C Hamano
2007-08-06 8:03 ` Shawn O. Pearce [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=20070806080301.GL9527@spearce.org \
--to=spearce@spearce.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.