{"thread":{"id":"16273","subject":"Forcing encoding for \"git commit\"","startedAt":"2008-11-11T17:10:46Z","lastAt":"2008-11-11T17:10:46Z","messageCount":1,"participants":["Constantine Plotnikov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"95466","messageId":"85647ef50811110910p7b40fd5dhcd79f8ae38709b95@mail.gmail.com","threadId":"16273","inReplyTo":null,"subject":"Forcing encoding for \"git commit\"","fromName":"Constantine Plotnikov","fromEmail":"constantine.plotnikov@gmail.com","sentAt":"2008-11-11T17:10:46Z","receivedAt":"2008-11-11T17:10:46Z","isPatch":false,"sender":{"key":"constantine.plotnikov@gmail.com","avatar":null},"body":"I would like to see a possibility to force encoding for the \"git\ncommit\" command. Currently only way to change encoding used by \"git\ncommit\" is to set \"i18n.commitencoding\" configuration variable. But\nthere is no way to override this variable for the specific commit like\nit is possible for \"show\" and \"log\" commands.\n\nThis would be useful when git is invoked from the tools. Currently\ntools have to query configuration variable and to encode message\naccording to the value of the variable. And it might happen that not\nall characters produced by tool are supported by target encoding.\nForcing the encoding, would have allowed the tool use the suitable\nencoding without changing user preferences.\n\nRegards,\nConstantine\n"}]}