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 independent
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 the affeced area
Junio C Hamano gits...@pobox.com 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
...@iee.org, Duy Nguyen pclo...@gmail.com, Jonathan
Nieder jrnie...@gmail.com
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: [PATCH 1/2
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 kel...@shysecurity.com
---
Documentation/diff-options.txt | 4
diff.c | 2 ++
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 kel...@shysecurity.com
---
Documentation/diff-options.txt | 4
diff.c | 2 ++
6 matches
Mail list logo