From: Kazutoshi Satoda <k_satoda@f2.dion.ne.jp>
To: git@vger.kernel.org
Cc: normalperson@yhbt.net, alex.crezoff@gmail.com
Subject: [PATCH 0/2] enable "svn.pathnameencoding" on dcommit
Date: Tue, 9 Feb 2016 00:19:06 +0900 [thread overview]
Message-ID: <56B8B1EA.5020901@f2.dion.ne.jp> (raw)
These are small fixes to problems I encountered using git-svn with
svn.pathnameencoding configuration (cp932 in my case). The problems
happen only when sending changes on non-ASCII paths.
I'm sorry not coming with test scripts, but I couldn't figure out how to
write tests to reproduce problems happen only with non-UTF-8 paths while
the tests seems to be run on UTF-8 locale.
I just ran existing tests with these fixes and there was no breakage
(with UTF-8 locale).
I think sending these fixes as-is is better than not sending because of
my lack of ability to write such tests. I also expect that these fixes
can be applied as-is because there were some small fixes without tests
in the history of file perl/Git/SVN/Editor.pm.
The first one is an updated fix of an very old but not applied patch.
http://comments.gmane.org/gmane.comp.version-control.git/164166#o2
The second one can be seen as a separate fix, but it takes effect only
after the first one.
Kazutoshi SATODA (2):
git-svn: enable "svn.pathnameencoding" on dcommit
git-svn: apply "svn.pathnameencoding" before URL encoding
perl/Git/SVN/Editor.pm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.7.0
next reply other threads:[~2016-02-08 15:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 15:19 Kazutoshi Satoda [this message]
2016-02-08 15:20 ` [PATCH 1/2] git-svn: enable "svn.pathnameencoding" on dcommit 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
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=56B8B1EA.5020901@f2.dion.ne.jp \
--to=k_satoda@f2.dion.ne.jp \
--cc=alex.crezoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.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.