David Aguilar <davvid@xxxxxxxxx> writes:
> I have a poor imagination and cannot imagine why it needs to be
> switchable.
I could not either, but I found the reason in the commit message:
eff80a9fd990
Some users do want to write a line that begin with a pound sign, #,
in their commit log message. Many tracking system recognise
a token of #<bugid> form, for example.
The support we offer these use cases is not very friendly to the end
users. They have a choice between
- Don't do it. Avoid such a line by rewrapping or indenting; and
- Use --cleanup=whitespace but remove all the hint lines we add.
Give them a way to set a custom comment char, e.g.
$ git -c core.commentchar="%" commit
so that they do not have to do either of the two workarounds.
I personnally think allowing an escape scheme (\#) would have been
better.
But as Junio said, it's too late. My change is not about commentchar
customizability, but about disabling the comment in "git status".
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
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