From: Esko Luontola <esko.luontola@gmail.com>
To: git@vger.kernel.org
Subject: Re: Cross-Platform Version Control
Date: Tue, 12 May 2009 18:06:05 +0300 [thread overview]
Message-ID: <419AD153-53B4-4DAB-AF72-4127C17B1CA0@gmail.com> (raw)
A good start for making Git cross-platform, would be storing the text
encoding of every file name and commit message together with the
commit. Currently, because Git is oblivious to the encodings and just
considers them as a series of bytes, there is no way to make them
cross-platform. It's as http://www.joelonsoftware.com/articles/Unicode.html
says, "It does not make sense to have a string without knowing what
encoding it uses." Without explicit encoding information, making a
system that works even on the three main platforms, let alone in all
countries and languages, is simply not possible.
On the other hand, if the encoding is explicitly stated in the
repository, then it is possible for platform and locale aware Git
clients to handle the file names and commit messages in whatever way
makes most sense for the platform (for example convert the file names
to the platform's encoding, if it differs from the committer's
platform encoding). Then it would also be possible to create a Mac
version of Git, which compensates for Mac OS X's file system's file
name encoding peculiarities. Also the system could then warn (on "git
add") if the data does not look like it has been encoded with the said
encoding.
If the platform's and the repository's encoding happen to be the same
(which in reality might be possible only inside a small company where
everybody is forced to use the same OS and is configured by a single
sysadmin), then no conversions need to be done. Also Git purists, who
think that the byte sequence representing a file name are more
important than the human readable version of the file name, may use
some configuration switch that disables all conversions - but even
then the current encoding should be stored together with the commit.
Are there any plans on storing the encoding information of file names
and commit messages in the Git repository? How much time would
implementing it take? Any ideas on how to maintain backwards
compatibility (for old commits that do not have the encoding
information)?
- Esko
next reply other threads:[~2009-05-12 15:07 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:06 Esko Luontola [this message]
2009-05-12 15:14 ` Cross-Platform Version Control Shawn O. Pearce
2009-05-12 16:13 ` Johannes Schindelin
2009-05-12 17:56 ` Esko Luontola
2009-05-12 20:38 ` Johannes Schindelin
2009-05-12 21:16 ` Esko Luontola
2009-05-13 0:23 ` Johannes Schindelin
2009-05-13 5:34 ` Esko Luontola
2009-05-13 6:49 ` Alex Riesen
2009-05-13 10:15 ` Johannes Schindelin
[not found] ` <43d8ce650905130340q596043d5g45b342b62fe20e8d@mail.gmail.com>
2009-05-13 10:41 ` John Tapsell
2009-05-13 13:42 ` Jay Soffian
2009-05-13 13:44 ` Alex Riesen
2009-05-13 13:50 ` Jay Soffian
2009-05-13 13:57 ` John Tapsell
2009-05-13 15:27 ` Nicolas Pitre
2009-05-13 16:22 ` Johannes Schindelin
2009-05-13 17:24 ` Andreas Ericsson
2009-05-14 1:49 ` Miles Bader
2009-05-12 16:16 ` Jeff King
2009-05-12 16:57 ` Johannes Schindelin
2009-05-13 16:26 ` Linus Torvalds
2009-05-13 17:12 ` Linus Torvalds
2009-05-13 17:31 ` Andreas Ericsson
2009-05-13 17:46 ` Linus Torvalds
2009-05-13 18:26 ` Martin Langhoff
2009-05-13 18:37 ` Linus Torvalds
2009-05-13 21:04 ` Theodore Tso
2009-05-13 21:20 ` Linus Torvalds
2009-05-13 21:08 ` Daniel Barkalow
2009-05-13 21:29 ` Linus Torvalds
2009-05-13 20:57 ` Matthias Andree
2009-05-13 21:10 ` Linus Torvalds
2009-05-13 21:30 ` Jay Soffian
2009-05-13 21:47 ` Matthias Andree
2009-05-12 18:28 ` Dmitry Potapov
2009-05-12 18:40 ` Martin Langhoff
2009-05-12 18:55 ` Jakub Narebski
2009-05-12 21:43 ` [PATCH] Extend sample pre-commit hook to check for non ascii file/usernames Heiko Voigt
2009-05-12 21:55 ` Jakub Narebski
2009-05-14 17:59 ` [PATCH v2] Extend sample pre-commit hook to check for non ascii filenames Heiko Voigt
2009-05-15 10:52 ` Martin Langhoff
2009-05-18 9:37 ` Heiko Voigt
2009-05-18 22:26 ` Jakub Narebski
2009-06-20 12:14 ` [RFC PATCH] check for filenames that only differ in case to sample pre-commit hook Heiko Voigt
2009-05-15 14:57 ` [PATCH v2] Extend sample pre-commit hook to check for non ascii filenames Jakub Narebski
2009-05-18 9:50 ` [PATCH] " Heiko Voigt
2009-05-18 10:40 ` Johannes Sixt
2009-05-18 11:50 ` Heiko Voigt
2009-05-18 12:04 ` Johannes Sixt
2009-05-19 20:01 ` [PATCH v4] " Heiko Voigt
2009-05-18 14:42 ` [PATCH] " Junio C Hamano
2009-05-18 20:35 ` Julian Phillips
2009-05-15 18:11 ` [PATCH v2] " Junio C Hamano
2009-05-14 13:48 ` Cross-Platform Version Control Peter Krefting
2009-05-14 19:58 ` Esko Luontola
2009-05-14 20:21 ` Andreas Ericsson
2009-05-14 22:25 ` Johannes Schindelin
2009-05-15 11:18 ` Dmitry Potapov
-- strict thread matches above, loose matches on Subject: below --
2009-04-27 8:55 Eric Sink's blog - notes on git, dscms and a "whole product" approach Martin Langhoff
2009-04-28 11:24 ` Cross-Platform Version Control (was: Eric Sink's blog - notes on git, dscms and a "whole product" approach) Jakub Narebski
2009-04-29 6:55 ` Martin Langhoff
2009-04-29 7:52 ` Cross-Platform Version Control Jakub Narebski
2009-04-29 8:25 ` Martin Langhoff
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=419AD153-53B4-4DAB-AF72-4127C17B1CA0@gmail.com \
--to=esko.luontola@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.