Re: [PATCH v4 1/3] Add test to describe expectation of blame --reverse with branched history

2015-10-27 Thread Junio C Hamano
Max Kirillov writes: >> The explanation of the first paragraph needs to be rewritten to make >> it understandable, but I am not sure what relevance it has with this >> change. > ... > So the history looks rather like (the interesting line is removed > in B1, line removal is

Re: [PATCH v4 1/3] Add test to describe expectation of blame --reverse with branched history

2015-10-26 Thread Junio C Hamano
Max Kirillov writes: > If history contains merges from feature branches, `blame --reverse` > reports not the commit when the line was actually edited, but head of > the last merged branch which was created before the edit. > > As a workaround, `blame --reverse --first-parent`

Re: [PATCH v4 1/3] Add test to describe expectation of blame --reverse with branched history

2015-10-26 Thread Max Kirillov
On Sun, Oct 25, 2015 at 11:27:32PM -0700, Junio C Hamano wrote: > Max Kirillov writes: > >> If history contains merges from feature branches, `blame --reverse` >> reports not the commit when the line was actually edited, but head of >> the last merged branch which was created

[PATCH v4 1/3] Add test to describe expectation of blame --reverse with branched history

2015-10-25 Thread Max Kirillov
If history contains merges from feature branches, `blame --reverse` reports not the commit when the line was actually edited, but head of the last merged branch which was created before the edit. As a workaround, `blame --reverse --first-parent` could be used to find the merge of branch

Re: [PATCH v4 1/3] Add test to describe expectation of blame --reverse with branched history

2015-10-25 Thread Max Kirillov
Sorry, forgot to fix the tests. Will send another batch some later. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html