On Thu, Jul 27, 2017 at 11:27 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> Well, we could also try a "zebra" as in sb/diff-color-move to show blocks
>> with the same fancy border detection.
>
> Luckily, blame output has places for metainfo on each line, unlike
> diff output, so there w
Stefan Beller writes:
> Well, we could also try a "zebra" as in sb/diff-color-move to show blocks
> with the same fancy border detection.
Luckily, blame output has places for metainfo on each line, unlike
diff output, so there won't be a need for painting border
differently. For example, if we
On Wed, Jul 26, 2017 at 4:29 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> When using git-blame lots of lines contain redundant information, for
>> example in hunks that consist of multiple lines, the metadata (commit name,
>> author) are repeated. A reader may not be interested in those
Stefan Beller writes:
> When using git-blame lots of lines contain redundant information, for
> example in hunks that consist of multiple lines, the metadata (commit name,
> author) are repeated. A reader may not be interested in those, so darken
> (commit, author) information that is the same as
When using git-blame lots of lines contain redundant information, for
example in hunks that consist of multiple lines, the metadata (commit name,
author) are repeated. A reader may not be interested in those, so darken
(commit, author) information that is the same as in the previous line.
Choose a
5 matches
Mail list logo
