From: David Woodhouse <dwmw2@infradead.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>, git@vger.kernel.org
Subject: Re: OT: character encodings
Date: Mon, 08 Jan 2007 09:53:51 +0800 [thread overview]
Message-ID: <1168221232.14763.80.camel@shinybook.infradead.org> (raw)
In-Reply-To: <45A17645.1030905@imap.cc>
On Sun, 2007-01-07 at 23:37 +0100, Tilman Schmidt wrote:
> > That depends on your point of view. David's assertion was that git
> > internally uses UTF-8.
>
> Well, I'm inclined to say he was wrong. Git internally is completely
> oblivious to character encoding.
See the 'i18n.commitencoding' property, stored in the repository config
and defaulting to UTF-8. Git is certainly capable of converting to its
internal storage encoding when you commit; if it doesn't do so by
default then that would be a bug.
--
dwmw2
prev parent reply other threads:[~2007-01-08 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0701062216210.3661@woody.osdl.org>
[not found] ` <Pine.LNX.4.61.0701071152570.4365@yvahk01.tjqt.qr>
[not found] ` <20070107114439.GC21613@flint.arm.linux.org.uk>
[not found] ` <45A0F060.9090207@imap.cc>
[not found] ` <1168182838.14763.24.camel@shinybook.infradead.org>
[not found] ` <20070107153833.GA21133@flint.arm.linux.org.uk>
[not found] ` <20070107182151.7cc544f3@localhost.localdomain>
[not found] ` <20070107191730.GD21133@flint.arm.linux.org.uk>
[not found] ` <20070107200553.GA15101@redhat.com>
2007-01-07 20:15 ` OT: character encodings (was: Linux 2.6.20-rc4) Sean
2007-01-07 20:40 ` Jan Engelhardt
2007-01-07 21:07 ` Xavier Bestel
[not found] ` <1168187346.14763.70.camel@shinybook.infradead.org>
[not found] ` <20070107170656.GC21133@flint.arm.linux.org.uk>
[not found] ` <45A14A2A.9060306@imap.cc>
[not found] ` <20070107195051.GF21133@flint.arm.linux.org.uk>
[not found] ` <45A17645.1030905@imap.cc>
2007-01-08 1:53 ` David Woodhouse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1168221232.14763.80.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tilman@imap.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).