I built from source and was unable to find a git version where this
has ever worked correctly.
I wasn't able to compile and test versions older than 1.6.1.
Confirmed not working:
2.15.1
2.13.6 (Apple Git-96)
2.0.0
1.7.0
1.6.3
1.6.2
1.6.1
I updated the https://github.com/nicksnyder/git-blame-bug
> Can you bisect to see when the feature stopped working as you expect?
I will see if I can do that but might take some time.
> It finds up to which commit each line survived without getting touched since
> the oldest commit in the range.
Right, this is where it is failing in my case.
With a h
Nick Snyder writes:
> This can be reproduced on Linux and Mac. This behavior seems to be a bug.
Can you bisect to see when the feature stopped working as you expect?
Unlike a forward blame, where the command tries to find a commit
that is responsible for a line being in the final result (i.e.
t
This can be reproduced on Linux and Mac. This behavior seems to be a bug.
On Wed, Nov 29, 2017 at 12:06 AM, Nick Snyder wrote:
> I have a repo that reproduces a behavior with `git blame --reverse`
> that surprises me. https://github.com/nicksnyder/git-blame-bug
>
> The readme explains the observe
I have a repo that reproduces a behavior with `git blame --reverse`
that surprises me. https://github.com/nicksnyder/git-blame-bug
The readme explains the observed behavior and what I expected to
happen. I will inline the readme at the bottom of this message for
convenience.
Am I misunderstanding
5 matches
Mail list logo
