From: "Shawn O. Pearce" <spearce@spearce.org>
To: Peter Krefting <peter@softwolves.pp.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [GIT-GUI PATCH] Correctly launch gitk for branch whose name matches a local file
Date: Sat, 23 Jan 2010 14:41:31 -0800 [thread overview]
Message-ID: <20100123224131.GD12679@spearce.org> (raw)
In-Reply-To: <20100121121848.BE37D2FC47@perkele>
Peter Krefting <peter@softwolves.pp.se> wrote:
> When trying to run gitk on a branch name whose name matches a local file,
> it will toss an error saying that the name is ambiguous. Adding a pair
> of dashes will make gitk parse the options to the left of it as branch
> names. Since wish eats the first pair of dashes we throw at it, we need
> to add a second one to ensure they get through.
>
> Signed-off-by: Peter Krefting <peter@softwolves.pp.se>
> ---
> git-gui.sh | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Thanks, applied.
--
Shawn.
prev parent reply other threads:[~2010-01-23 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 12:15 [GIT-GUI PATCH] Correctly launch gitk for branch whose name matches a local file Peter Krefting
2010-01-23 22:41 ` 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=20100123224131.GD12679@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
/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).