kel...@shysecurity.com writes:
>>> Content-Type: text/plain; charset=utf-8; format=flowed
>>Please. No format=flawed. Really.
> I'll figure out the line-wrapping.
>
>> Also this step is not about --no-relative and diff.relative but is
>> only about --no-relative option.
> Should I submit as two
Junio C Hamano writes:
> Patch 2/2 also seems to share similar line-wrapping breakages that
> make it unappliable, but more importantly, the configuration that is
> supposed to correspond to --relative option only parses a boolean.
> Is that the right design, or should it also be able to substitu
ecurity.com
CC: Git Mailing List , Philip Oakley
, Duy Nguyen , Jonathan
Nieder
Subject: Re: [PATCH 1/2] support for --no-relative and diff.relative
kel...@shysecurity.com writes:
Content-Type: text/plain; charset=utf-8; format=flowed
Please. No format=flawed. Really.
Subject: Re: [PA
kel...@shysecurity.com writes:
> Content-Type: text/plain; charset=utf-8; format=flowed
Please. No format=flawed. Really.
> Subject: Re: [PATCH 1/2] support for --no-relative and diff.relative
"diff: teach --no-relative to override earlier --relative" or
something. Saying
added --no-relative option for git-diff (code, documentation, and tests)
--no-relative overrides --relative causing a return to standard behavior
Signed-off-by: Brandon Phillips
---
Documentation/diff-options.txt | 4
diff.c | 2 ++
t/t4045-diff-relative.sh
added --no-relative option for git-diff (code, documentation, and tests)
--no-relative overrides --relative causing a return to standard behavior
Signed-off-by: Brandon Phillips
---
Documentation/diff-options.txt | 4
diff.c | 2 ++
t/t4045-diff-relative.sh
6 matches
Mail list logo