From: Eric Wong <normalperson@yhbt.net>
To: Kazutoshi Satoda <k_satoda@f2.dion.ne.jp>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, alex.crezoff@gmail.com
Subject: Re: [PULL] svn pathnameencoding for git svn dcommit
Date: Sat, 20 Feb 2016 23:37:43 +0000 [thread overview]
Message-ID: <20160220233743.GA28606@dcvr.yhbt.net> (raw)
In-Reply-To: <56C34BFF.3030301@f2.dion.ne.jp>
Kazutoshi Satoda <k_satoda@f2.dion.ne.jp> wrote:
> (Shouldn't the branch be based on maint, as these are bugfixes?)
I'm not sure if it being previously left-out/untested feature
would qualify for maint. Maybe it does, but I suppose I'll let
Junio decide.
> Thank you. I tried it but got similar problem:
<snip>
> I found how "\357\202\201\357\202\202" (U+F081 U+F082 in UTF-8) could
> come.
> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars
> > Some characters are disallowed in filenames on Windows filesystems. ...
> ...
> > ... All of the above characters, except for the backslash, are converted
> > to special UNICODE characters in the range 0xf000 to 0xf0ff (the
> > "Private use area") when creating or accessing files.
> "U+F081 U+F082" seems the result of conversion from "0x8182" (neq in
> cp932) as treating each of 2 bytes as disallowed characters.
>
> And I also noticed that LANG and LC_ALL is set to "C" in test-lib.sh.
>
> Setting LC_ALL=C.UTF-8 in the test 11-12 made them pass on Cygwin.
> Same change made the previous version also pass. Please find the patch
> in the attached output of git format-patch.
Thanks. However, I also wonder what happens on machines without
"C.UTF-8" support (are there still any?).
> Could you please test with this on non-Cygwin environment?
Works for me, at least. I've squashed your changes into the two
patches already queued up. I needed to split the
"export LC_ALL=C.UTF-8" statement into
"LC_ALL=C.UTF-8 && export LC_ALL" for portability.
> If it made no harm, please tell me what should I do to proceed this patch.
> Will you (Eric) please make further integration? Shall I make another
> series (v2) of patches?
I've pushed out a new branch with your LC_ALL changes squashed
in. However I'm unsure if there's any new portability problems
with LC_ALL=C.UTF-8...
Junio or anyone else: thoughts?
The following changes since commit 0233b800c838ddda41db318ee396320b3c21a560:
Merge branch 'maint' (2016-02-17 10:14:39 -0800)
are available in the git repository at:
git://bogomips.org/git-svn.git ks/svn-pathnameencoding-3
for you to fetch changes up to 980c083276ba06a9400c5b1b2558c3626bcff969:
git-svn: apply "svn.pathnameencoding" before URL encoding (2016-02-20 23:30:16 +0000)
----------------------------------------------------------------
Kazutoshi Satoda (2):
git-svn: enable "svn.pathnameencoding" on dcommit
git-svn: apply "svn.pathnameencoding" before URL encoding
perl/Git/SVN/Editor.pm | 4 +++-
t/t9115-git-svn-dcommit-funky-renames.sh | 39 ++++++++++++++++++++++++++++++--
2 files changed, 40 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2016-02-20 23:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 15:19 [PATCH 0/2] enable "svn.pathnameencoding" on dcommit Kazutoshi Satoda
2016-02-08 15:20 ` [PATCH 1/2] git-svn: " Kazutoshi Satoda
2016-02-15 0:30 ` Eric Wong
2016-02-08 15:21 ` [PATCH 2/2] git-svn: apply "svn.pathnameencoding" before URL encoding Kazutoshi Satoda
2016-02-15 0:33 ` Eric Wong
2016-02-08 22:58 ` [PATCH 0/2] enable "svn.pathnameencoding" on dcommit Eric Wong
2016-02-15 0:52 ` [PULL] svn pathnameencoding for git svn dcommit Eric Wong
2016-02-15 21:32 ` Junio C Hamano
2016-02-16 3:29 ` Kazutoshi Satoda
2016-02-16 6:33 ` Eric Wong
2016-02-16 16:19 ` Kazutoshi Satoda
2016-02-20 23:37 ` Eric Wong [this message]
2016-02-21 13:12 ` Kazutoshi Satoda
2016-02-27 18:28 ` [PATCH 1/1] t9115: Skip pathnameencoding=cp932 under HFS tboegi
2016-02-28 4:59 ` Eric Wong
2016-02-28 17:52 ` Torsten Bögershausen
2016-03-15 1:59 ` Eric Wong
2016-03-15 5:23 ` Torsten Bögershausen
2016-03-15 7:09 ` Eric Wong
2016-03-16 17:37 ` Kazutoshi Satoda
2016-03-17 5:16 ` Torsten Bögershausen
2016-03-17 5:35 ` Torsten Bögershausen
2016-03-18 2:15 ` Kazutoshi Satoda
2016-03-19 6:59 ` Torsten Bögershausen
2016-03-18 2:14 ` Kazutoshi Satoda
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=20160220233743.GA28606@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=alex.crezoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=k_satoda@f2.dion.ne.jp \
/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).