From: Junio C Hamano <gitster@pobox.com>
To: Sam Vilain <sam.vilain@catalyst.net.nz>
Cc: git@vger.kernel.org, Peter Karlsson <peter@softwolves.pp.se>,
Mark Junker <mjscod@web.de>, Pedro Melo <melo@simplicidade.org>,
Martin Langhoff <martin.langhoff@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Dmitry Potapov <dpotapov@gmail.com>, Kevin Ballard <kevin@sb.org>
Subject: Re: [PATCH] [RFC] Design for pathname encoding gitattribute [RESEND]
Date: Mon, 21 Jan 2008 22:26:43 -0800 [thread overview]
Message-ID: <7vlk6iv0ik.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080122050215.DE198200A2@wilber.wgtn.cat-it.co.nz> (Sam Vilain's message of "Tue, 22 Jan 2008 17:41:59 +1300")
Sam Vilain <sam.vilain@catalyst.net.nz> writes:
> Some projects may like to enforce a particular encoding is used for
> all filenames in the repository. Within the UTF-8 encoding, there are
> four normal forms (see http://unicode.org/reports/tr15/), any of which
> may be a reasonable repository format choice. Additionally, some
> filesystems may have a single encoding that they support when writing
> local filenames. To support this, iconv and a normalization library
> must have the information they need to perform the correct conversion.
Isn't there a chicken-and-egg problem? The attributes are by
nature per-path, and you need to match the pathname string with
a pattern to decide which attribute definition to apply to a
given path. Before knowing what encoding the pathname you have
just read from readdir(3), how would you match that pathname
with the pattern in the gitattributes file?
I can buy the .git/config (and an in-tree .git-encoding,
perhaps), though.
next prev parent reply other threads:[~2008-01-22 6:27 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 [this message]
2008-01-22 7:43 ` Junio C Hamano
2008-01-22 8:09 ` Mark Junker
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=7vlk6iv0ik.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=kevin@sb.org \
--cc=martin.langhoff@gmail.com \
--cc=melo@simplicidade.org \
--cc=mjscod@web.de \
--cc=peter@softwolves.pp.se \
--cc=sam.vilain@catalyst.net.nz \
/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).