> I do not think we want to change the commit header Can you please explain why not ? > (1) git-am should default to -u; this was suggested on the list > long time ago, but is an incompatible change. v1.5.0 we > can afford to be incompatible to make it more usable and > safer. I use git-am rarely so can't comment on this > (2) update commit-tree to reject non utf-8 log messages and > author/committer names when i18n.commitEncoding is _NOT_ > set, or set to utf-8. > > Maybe later we can use encoding validation routines for > other encodings by checking i18n.commitEncoding, but at the > minimum the above would be safe enough for recommended UTF-8 > only cases. See the situation: 1. I have utf-8 encoded repo. 2. Somebody clone my repo, try to commit using non-utf-8 encoding, fail and change i18n.commitEncoding. When it commits something and ask me to pull. 3. I pull and got non-utf-8 commit message :-) - 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