From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
Cc: git@vger.kernel.org
Subject: Re: [BUG] gitk fails with argument that is both existing directory and branch name
Date: Tue, 3 Jul 2007 22:55:22 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707032248570.4071@racer.site> (raw)
In-Reply-To: <20070703202301.GA24071@informatik.uni-freiburg.de>
Hi,
On Tue, 3 Jul 2007, Uwe Kleine-K?nig wrote:
> zeisberg@cassiopeia:~/gsrc/linux-2.6$ git rev-list ^linus/master fixes
> fatal: ambiguous argument 'fixes': both revision and filename
> Use '--' to separate filenames from revisions
>
> but
>
> gitk ^linus/master fixes --
Umm. Why don't you just use gitk linus/master..fixes? This is how we teach
people to use rev-list anyway.
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-03 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 20:23 [BUG] gitk fails with argument that is both existing directory and branch name Uwe Kleine-König
2007-07-03 21:55 ` Johannes Schindelin [this message]
2007-07-03 22:17 ` Linus Torvalds
2007-07-03 22:44 ` Johannes Schindelin
2007-07-03 22:55 ` [PATCH] gitk: fix for "gitk <ambiguous-name> --" Johannes Schindelin
2007-07-04 7:37 ` Gerrit Pape
2007-07-04 8:38 ` Uwe Kleine-König
2007-07-04 10:44 ` Paul Mackerras
2007-07-04 16:58 ` 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=Pine.LNX.4.64.0707032248570.4071@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=ukleinek@informatik.uni-freiburg.de \
/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).