e-bug with a
script to easily reproduce.
On Wed, Dec 6, 2017 at 10:00 AM, Nick Snyder wrote:
>> 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 surviv
On Wed, Dec 6, 2017 at 9:22 AM, Junio C Hamano wrote:
> 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, whe
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
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
4 matches
Mail list logo