Wincent Colaiuta <win@xxxxxxxxxxx> writes:
> What are the other options?
>
> - Make git-add--interactive part of builtin-add so as to be able to
> use the core.whitespace code directly? (ideally yes and at some point
> in the future it seems inevitable that this will happen, but it will
> require a fair bit of work)
>
> - Fork a second "git diff-files" process to capture the colorized
> version of the output? (may set off the "kludge" alarm)
>
> - Something else?
- Realize that whitespace clean-up can be risky and change semantics
depending on the material you are editing. Do not do the clean-up
during "add -i", but before. IOW, add an alias that does an
equivalent of:
git diff HEAD >tmp
git apply -R <tmp
git apply --whitespace=fix <tmp
then encourage users to clean-up their whitespace gotchas early (and
test the result!), before even attempting to run "git add -i".
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
