On Wed, Jun 12, 2013 at 5:52 PM, Daniel Shahaf wrote:
> What about an optional output mode that prints the gaps only, but all of
> them?
>
> e.g., if I do 'blame -r 25:29', the optional output mode would print all
> lines added in r26 or in r27 or in r28 that are not present in r29, and
> only the
Julian Foad wrote on Wed, Jun 12, 2013 at 16:41:59 +0100:
> Prabhu wrote:
>
> > On 06/12/2013 05:55 PM, Julian Foad wrote:
> >> I have thought before that it would sometimes be useful to include blame
> >> information on the gaps between lines. For each gap between adjacent
> >> lines (and
>
Prabhu wrote:
> On 06/12/2013 05:55 PM, Julian Foad wrote:
>> I have thought before that it would sometimes be useful to include blame
>> information on the gaps between lines. For each gap between adjacent lines
>> (and
>> before the first and after the last line), there is a revision in whi
On Wed, Jun 12, 2013 at 2:25 PM, Julian Foad wrote:
> Markus Schaber wrote:
>
>> On Mon, Jun 10, 2013 at 01:38:48PM -, danie...@apache.org wrote:
>>> It would have been easy to find what revision removed the line break if we
>>> had a reverse blame --- that is, a blame that walks the chain of
On 06/12/2013 05:55 PM, Julian Foad wrote:
Markus Schaber wrote:
On Mon, Jun 10, 2013 at 01:38:48PM -, danie...@apache.org wrote:
It would have been easy to find what revision removed the line break if we
had a reverse blame --- that is, a blame that walks the chain of diffs from
newerto o
Markus Schaber wrote:
> On Mon, Jun 10, 2013 at 01:38:48PM -, danie...@apache.org wrote:
>> It would have been easy to find what revision removed the line break if we
>> had a reverse blame --- that is, a blame that walks the chain of diffs from
>> newerto older, rather than from older to ne
6 matches
Mail list logo
