From: Debayan Banerjee <debayanin@gmail.com>
To: git@vger.kernel.org
Subject: Possible bug with argument parsing in git blame
Date: Mon, 17 May 2010 15:51:18 +0530 [thread overview]
Message-ID: <AANLkTikn1-Ua6G7eAc8UD8DJx0vpc-5-BOoxsi2mx2BC@mail.gmail.com> (raw)
debayan@deep-blur:~/testrepo$ git blame 22621a32..8486802f --
dir/subdir/newsubdir/b
81531975 b (debayan 2010-05-13 15:32:17 +0530 1) four
81531975 b (debayan 2010-05-13 15:32:17 +0530 2) five
d700ac9c b (debayan 2010-05-13 15:33:27 +0530 3) blah
2656ab56 b (debayan 2010-05-13 15:33:34 +0530 4) bleh
d0c6e851 b (debayan 2010-05-13 15:42:21 +0530 5) foo
7bf5510e b (debayan 2010-05-13 15:42:53 +0530 6) yo
c4515289 b (debayan 2010-05-13 15:43:10 +0530 7) lala
a257c7e4 b (debayan 2010-05-13 16:03:46 +0530 8) yes
ed8e4601 b (debayan 2010-05-13 16:03:55 +0530 9) np
e96d14bf dir/subdir/newsubdir/b (debayan 2010-05-13 16:05:05 +0530 10) yo
dace00d1 dir/subdir/newsubdir/b (debayan 2010-05-13 16:05:11 +0530 11) boye
8486802f dir/subdir/newsubdir/b (debayan 2010-05-13 16:07:51 +0530 12) what?
debayan@deep-blur:~/testrepo$ git blame 22621a32..8486802f
dir/subdir/newsubdir/b
fatal: cannot stat path 22621a32..8486802f: No such file or directory
The only difference between the first and the second command is the
"--" separator. Is this normal behaviour?
--
Debayan Banerjee
Software Engineer
next reply other threads:[~2010-05-17 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 10:21 Debayan Banerjee [this message]
2010-05-23 8:00 ` Possible bug with argument parsing in git blame Jeff King
[not found] ` <AANLkTinMlvmOneGgkIqxE8qWlhoOlqgALl-YHprqPI6h@mail.gmail.com>
2010-05-23 20:08 ` Jeff King
2010-05-24 6:17 ` Debayan Banerjee
2010-05-24 6:46 ` Jeff King
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=AANLkTikn1-Ua6G7eAc8UD8DJx0vpc-5-BOoxsi2mx2BC@mail.gmail.com \
--to=debayanin@gmail.com \
--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).