git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Himpel <chressie@googlemail.com>
To: Jeff King <peff@peff.net>
Cc: Christian Himpel <chressie@googlemail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-am: force egrep to use correct characters set
Date: Mon, 28 Sep 2009 08:55:19 +0200	[thread overview]
Message-ID: <20090928065519.GA24773@lamagra.informatik.uni-ulm.de> (raw)
In-Reply-To: <20090927074015.GB15393@coredump.intra.peff.net>

On Sun, Sep 27, 2009 at 03:40:15AM -0400, Jeff King wrote:
> On Fri, Sep 25, 2009 at 06:43:20PM +0200, Christian Himpel wrote:
> 
> > According to egrep(1) the US-ASCII table is used when LC_ALL=C is set.
> > We do not rely here on the LC_ALL value we get from the environment.
> 
> Hmm. Probably makes sense here, as it is a wide enough range that it may
> pick up other stray non-ascii characters in other charsets (though as
> the manpage notes, the likely thing is to pick up A-Z along with a-z,
> which is OK here as we encompass both in our range).
> 
> There are two other calls to egrep with brackets (both in
> git-submodule.sh), but they are just [0-7], which is presumably OK in
> just about any charset.
> 
> Do you happen to know a charset in which this is a problem, just for
> reference?

No, I don't know any charset with stray ascii-chars.  I just listened
attentively, when I read the part about the mixed alphabet characters in
the grep(1) manpage.

I did some quick checks just now.  It seems the characters (' ' to '~')
are in any locale, offered by glibc, at the same place.

Maybe, we can just leave the charset as it is and ignore this patch,
until someone complains.


Regards,
chressie

> 
> -Peff

  reply	other threads:[~2009-09-28  6:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 15:14 [PATCH 1/2] git-am: fixed patch_format detection according to RFC2822 Christian Himpel
2009-09-25 15:17 ` [PATCH 2/2] git-am: force egrep to use correct characters set Christian Himpel
2009-09-25 15:45   ` [PATCH 2/2 v2] " Christian Himpel
2009-09-25 16:43     ` [PATCH] " Christian Himpel
2009-09-27  7:40       ` Jeff King
2009-09-28  6:55         ` Christian Himpel [this message]
2009-09-28  7:16           ` Jeff King
2009-09-28  8:12         ` Johannes Sixt
2009-09-28  9:32           ` Christian Himpel
2009-09-28  9:53             ` Johannes Sixt
2009-09-28 12:09               ` Christian Himpel

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=20090928065519.GA24773@lamagra.informatik.uni-ulm.de \
    --to=chressie@googlemail.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 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).