From: Santi Béjar <sbejar@gmail.com>
Date: Thu, 21 Dec 2006 10:11:15 GMT
Subject: Re: specify charset for commits (Was: [PATCH] Fix documentation copy&paste typo)
Message-ID: <8aa486160612210211n64dc2973jcc4e7670fec2cabc@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.63.0612211050450.19693@wbgn013.biozentrum.uni-wuerzburg.de>

On 12/21/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Thu, 21 Dec 2006, Uwe Kleine-König wrote:
>
> > Junio C Hamano wrote:
> > > Me, keyboard and Emacs screwed up and stored it in ISO-2022
> > > instead of UTF-8.  Sorry.
> > It's a pity, but too late to change.[1]
> >
> > What do you think about a patch that makes git-commit-tree call iconv on
> > its input to get it to UTF-8 (or any other charset).
>
> We had this discussion over and over again. Last time (I think) was here:
>
> http://article.gmane.org/gmane.comp.version-control.git/11710
>
> Summary: we do not want to force the use of utf8.
>

Maybe git could have an example of the hook "commit-msg" that checks
that the commit message is in certain charset.

Santi