Thomas Rast writes:
>> Even though I am moving from builtin/blame.c to line-log.c? I would
>> otherwise have to call from a rather lib-ish file into a "front
>
> You haven't sent any reply to this. Does that mean you agree? Would
> you prefer the shared file to be named something like line-ran
Junio C Hamano writes:
> Junio C Hamano writes:
>
>> Thomas Rast writes:
>>
>>> To save the user a lookup of the last line number, introduce $ as a
>>> shorthand for the last line. This is mostly useful to spell "until
>>> the end of the file" as '-L,$'.
>>
>> Doesn't "-L " or "-L ," do that a
Junio C Hamano writes:
> Thomas Rast writes:
>
>> To save the user a lookup of the last line number, introduce $ as a
>> shorthand for the last line. This is mostly useful to spell "until
>> the end of the file" as '-L,$'.
>
> Doesn't "-L " or "-L ," do that already? If it were
> to introduce
Thomas Rast writes:
> To save the user a lookup of the last line number, introduce $ as a
> shorthand for the last line. This is mostly useful to spell "until
> the end of the file" as '-L,$'.
Doesn't "-L " or "-L ," do that already? If it were
to introduce "-L $-4," or "-L$-4,+2", I would und
To save the user a lookup of the last line number, introduce $ as a
shorthand for the last line. This is mostly useful to spell "until
the end of the file" as '-L,$'.
Signed-off-by: Thomas Rast
---
Documentation/line-range-format.txt | 6 ++
line-log.c | 8
5 matches
Mail list logo
