From: Timur Sufiev <tsufiev@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] Add I18N-wrappers for low-level IO-routines
Date: Wed, 28 Oct 2009 21:01:21 +0300 [thread overview]
Message-ID: <4ae886f4.0b38560a.6cfb.5ac4@mx.google.com> (raw)
In-Reply-To: <20091027210817.GA1577@sigill.intra.peff.net>
> Hmm. Two questions about this series:
>
> 1. Patch 3/4 didn't seem to make it to the list. Presumably that is
> where you actually use these routines in git? Or are they just for
> mingw?
Yes, it actually haven't made it to the list. Perhaps this was due to
patch size: it was approx. 3300 lines long (BTW, what's the message size
limit?) So I've rewritten the patch to make it more compact, using mingw
approach with macros. Subj prefix for a patch series is 'PATCH I18N
filenames v2'.
> 2. I seem to recall that Linus added a filename translation layer for
> doing much more, like handling unicode normalizations (but I
> confess I haven't looked closely at that code). Should this be part
> of that system?
I've heard nothing about that :(. Could you point me directly at Linus'
changes?
> -Peff
--
Timur Sufiev
next prev parent reply other threads:[~2009-10-28 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 13:54 [PATCH 1/4] Add routines for filenames encoding <local encoding> <-> UTF-8 Timur Sufiev
2009-10-27 13:54 ` [PATCH 2/4] Add I18N-wrappers for low-level IO-routines Timur Sufiev
[not found] ` <1256651643-18382-3-git-send-email-timur@iris-comp.ru>
2009-10-27 13:54 ` [PATCH 4/4] Make mingw-compatibility layer to be aware of I18N-wrappers Timur Sufiev
2009-10-27 21:08 ` [PATCH 2/4] Add I18N-wrappers for low-level IO-routines Jeff King
2009-10-28 18:01 ` Timur Sufiev [this message]
2009-10-28 18:10 ` Jeff King
2009-10-27 14:16 ` [PATCH 1/4] Add routines for filenames encoding <local encoding> <-> UTF-8 Peter Krefting
2009-10-28 7:15 ` Timur Sufiev
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=4ae886f4.0b38560a.6cfb.5ac4@mx.google.com \
--to=tsufiev@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.