|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
As far as I can tell from the git commit man page indicate that the contents of the git commit log are assumed to be UTF-8. That assumed character encoding is overridden if i18n.commitencoding is set.
The value of i18n.logoutputencoding is allowed to alter the encoding coming from the "git log", "git show" and "git blame" commands, allowing an override of the i18n.commitencoding value.
Unfortunately, I don't think there are currently any tests in the git-client-plugin or the git-plugin which test interesting combinations of those variables. It seems like a good area for a parameterized JUnit test.