git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: [BUG] gitk fails with argument that is both existing directory and branch name
Date: Tue, 3 Jul 2007 22:23:01 +0200	[thread overview]
Message-ID: <20070703202301.GA24071@informatik.uni-freiburg.de> (raw)

Hello,

I have a branch named fixes in my linux repo and until I did:

	git format-patch -o fixes linus/master 

the following command worked fine:
	
	gitk ^linus/master fixes

but now that there is a directory named fixes, nothing happens when
running gitk.  With rev-list I get 

	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 --

doesn't work either.  I'd suspect that the call to rev-list doesn't see
the "--" and the error is lost somewhere inbetween ...?

I currently have no time to look into it, so for now you only get a
report.

Best regards
Uwe

-- 
Uwe Kleine-König

http://www.google.com/search?q=i+squared

             reply	other threads:[~2007-07-03 20:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 20:23 Uwe Kleine-König [this message]
2007-07-03 21:55 ` [BUG] gitk fails with argument that is both existing directory and branch name Johannes Schindelin
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=20070703202301.GA24071@informatik.uni-freiburg.de \
    --to=ukleinek@informatik.uni-freiburg.de \
    --cc=git@vger.kernel.org \
    /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).