On Fri, 18 Nov 2005, H. Peter Anvin wrote:
Similarly, it may not be a bad idea to add an *option* -- now when we have a
config file mechanism -- to signal error on invalid UTF-8 import. This would
keep a correct UTF-8 repository from getting inadvertently messed up.
This I agree with, btw. We could easily have a
[core]
utf=1
thing, and make git-commit-tree refuse to commit a non-UTF8 message.
Of course, you could equally easily (more so?) make it just a commit
trigger instead, which might well be the right thing.
(And that still leaves the question open what to do about patches and
pulls, but if people mainly worry about newly written commit messages
itself, then at least that part is unambiguous).
Linus