git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard MICHAEL <rmichael@leadformance.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-filter-branch : LANG / LC_ALL = C breaks UTF-8 author names
Date: Fri, 20 Aug 2010 15:44:10 +0200	[thread overview]
Message-ID: <4C6E86AA.2020903@leadformance.com> (raw)
In-Reply-To: <20100820133244.GB15736@burratino>

  On 10-08-20 3:32 PM, Jonathan Nieder wrote:
> Richard MICHAEL wrote:
>
>> I am filtering our repo with git-filter-branch, but as the sed
>> script runs with LANG=C LC_ALL=C (7 bit US ASCII), it dies on
>> commits authored by our team members with accented names.
> Yep, someone else recently sent a report about such a sed version,
> too.  It is breaking our fragile minds; we ought to find some way to
> deal with it, but we haven't yet.
>
> Jonathan

Jonathan, thanks for your reply.

What about special casing the bad sed (or whitelisting good sed)?  
Surely a hack, but would those of us with GNU or BSD would be happy.  
Which was the troublesome sed?

That opposed to figuring out the problem, reading about unicode, and 
re-cloning and re-filtering 5,000 commits. :-)  Unfortunately, it 
doesn't "die" well either; the 'export' shell var fails but it keeps 
processing commits.  (If I hadn't investigated and changed the LANG, 
would I have lost those commits?)

Regards,
Richard

  reply	other threads:[~2010-08-20 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 13:20 git-filter-branch : LANG / LC_ALL = C breaks UTF-8 author names Richard MICHAEL
2010-08-20 13:32 ` Jonathan Nieder
2010-08-20 13:44   ` Richard MICHAEL [this message]
2010-09-01  1:08     ` Jonathan Nieder

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=4C6E86AA.2020903@leadformance.com \
    --to=rmichael@leadformance.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@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).