Junio C Hamano wrote: > Alexander Litvinov <litvinov2004@xxxxxxxxx> writes: > > > May we can add new header into commit with commit text encoding ? > > I do not think we want to change the commit header, nor we would > want to re-encode, but I can see two possible improvements: > > (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. > > (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. As I only want to use UTF-8 both suggestions are fine for me. Is there a generic way to check an encoding? (I don't know if there is an encoding that can encode everything. If so, we could use iconv -f $enc -t superencoding. Until now I thought UTF-8 can do, but in the post Johannes pointed out, you (Junio) implyed that it cannot.) Best regards Uwe -- Uwe Kleine-König dd if=/proc/self/exe bs=1 skip=1 count=3 2>/dev/null - 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