From: Mark Junker <mjscod@web.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] [RFC] Design for pathname encoding gitattribute [RESEND]
Date: Tue, 22 Jan 2008 09:09:33 +0100 [thread overview]
Message-ID: <fn48bp$ff8$1@ger.gmane.org> (raw)
In-Reply-To: <7vr6gatidd.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
> To support the above scenarios, I think each instance of
> repository needs to be able to say "this path (specified with a
> matching pattern in the filename encoding) should be converted
> this way coming in, and that way going out." UTF-8 only project
> would have NKC<->NKD on HFS+ partition, and nothing on
> everywhere else. EUC-JP project that checks out as-is would
> specify nothing either, but people on Shift_JIS platforms would
> locally specify that EUC-JP <-> Shift_JIS conversion to be made.
Just to sum up what you wrote and to be sure that I understand you
correctly:
Lets have two encodings:
- Encoding for path names stored in the repository
- Encoding for path names from/to file systems
Do conversion only if they are different. Both encodings are configurable.
Regards,
Mark
next prev parent reply other threads:[~2008-01-22 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 4:41 [PATCH] [RFC] Design for pathname encoding gitattribute [RESEND] Sam Vilain
2008-01-22 5:35 ` Johannes Schindelin
2008-01-22 6:37 ` Junio C Hamano
2008-01-22 6:26 ` Junio C Hamano
2008-01-22 7:43 ` Junio C Hamano
2008-01-22 8:09 ` Mark Junker [this message]
2008-01-22 9:16 ` Junio C Hamano
2008-01-22 9:13 ` Rafael Garcia-Suarez
2008-01-22 9:57 ` Sam Vilain
2008-01-22 10:36 ` Junio C Hamano
2008-01-22 10:44 ` Sam Vilain
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='fn48bp$ff8$1@ger.gmane.org' \
--to=mjscod@web.de \
--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 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).