git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: James North <tocapicha@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Encoding problems using git-svn
Date: Sun, 2 Nov 2008 01:48:45 -0800	[thread overview]
Message-ID: <20081102094845.GB16003@untitled> (raw)
In-Reply-To: <8b168cfb0810300814i53a264c2x997543e145d5e15a@mail.gmail.com>

James North <tocapicha@gmail.com> wrote:
> Hi Eric,
> 
> Don't worry about not seeing the patch and thanks for the answer :)
> 
> Your patch works great.
> 
> Messages appear without problems on "svn log" and "git log", I haven't
> found any gotcha that I know of.

Thanks for the confirmation.

> The weird thing is that this problem was not found by anyone before, I
> guessed there should be some people with a setup similar to mine.

Squeaky wheel gets the grease :)

Honestly, I think most folks have just moved onto UTF-8 entirely and
left legacy encodings behind.  Especially people using modern tools like
git (along with SVN enforcing UTF-8 at the repository/protocol level).


Junio:

I've pushed the following out to git://git.bogomips.org/git-svn.git:

Eric Wong (2):
      git-svn: don't escape tilde ('~') for http(s) URLs
      git-svn: respect i18n.commitencoding config

I'll try to get around to the more robust escaping checks
and splitting out the monolithic git-svn.perl source next
week.

-- 
Eric Wong

  reply	other threads:[~2008-11-02  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  3:14 Encoding problems using git-svn James North
2008-10-30  3:28 ` James North
2008-10-30  7:41 ` Eric Wong
2008-10-30 15:14   ` James North
2008-11-02  9:48     ` Eric Wong [this message]
2008-11-02 13:45       ` Robin Rosenberg

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=20081102094845.GB16003@untitled \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tocapicha@gmail.com \
    /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).