Re: Possible bug with argument parsing in git blame

From: Jeff King <peff@peff.net>
Date: May 23, 2010, 20:08 UTC
Message-ID: <20100523200853.GA23377@coredump.intra.peff.net>
In-Reply-To: <AANLkTinMlvmOneGgkIqxE8qWlhoOlqgALl-YHprqPI6h@mail.gmail.com>

On Sun, May 23, 2010 at 07:22:41PM +0530, Debayan Banerjee wrote:

Show 8 quoted lines

> > I can't reproduce the problem here. For example, in git.git, both of the
> > following produce the same output:
> >
> >  git blame HEAD~5..HEAD~3 alloc.c
> >  git blame HEAD~5..HEAD~3 -- alloc.c
> 
> It seems to happen only if the path has '/' in it. For example alloc.c
> will be parsed fine, but dir/alloc.c wont.

Sorry, I still can't reproduce with:

  mkdir repo && cd repo && git init
  mkdir subdir

  commit() {
    echo content >>subdir/file
    git add subdir/file
    git commit -m foo
  }

  commit; commit; commit; commit; commit

  git blame HEAD~3..HEAD~1 subdir/file >no-dash &&
  git blame HEAD~3..HEAD~1 -- subdir/file >dash &&
  diff no-dash dash &&
  echo ok

So there must be some difference between your setup and my test case. Can you give more details?

-Peff

PS I tested on a variety of git versions back to v1.5.5, and I couldn't trigger the problem, so I don't think it is a version issue.