All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fix linker generated lists on non-C locales
Date: Sun, 2 Dec 2012 20:15:01 +0100	[thread overview]
Message-ID: <201212022015.01618.marex@denx.de> (raw)
In-Reply-To: <1401096.DqHEXA3RTS@bloomfield>

Dear Pavel Herrmann,

[...]

> > > > > -	LC_COLLATE=C sort -u | \
> > > > > +	LC_ALL=C sort -u | \
> > > > 
> > > > How will this work? LC_COLLATE is supposed to adjust the behavior of
> > > > "sort" command, without it, "sort" will not behave as expected.
> > > 
> > > Clearly, LC_COLLATE is not enough for it to behave correctly, as seen
> > > on my
> > > setup.
> > > This works because LC_ALL sets LC_COLLATE, as well as all other LC_*
> > > environment variables.
> > 
> > Do you have any reference where I can verify this claim please?
> 
> Actually, the problem seems to be a little different - when i have LC_ALL
> set, changing LC_COLLATE doesnt do anything (try running "LC_COLLATE=crazy
> locale" with LC_ALL set)
> anyways, the fix remains the same.

Ugh, can you please provide any relevant documentation? Besides, is the commit 
message wrong now?

Best regards,
Marek Vasut

  reply	other threads:[~2012-12-02 19:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02 17:43 [U-Boot] [PATCH] fix linker generated lists on non-C locales Pavel Herrmann
2012-12-02 17:50 ` Marek Vasut
2012-12-02 18:00   ` Pavel Herrmann
2012-12-02 18:12     ` Marek Vasut
2012-12-02 18:26       ` Pavel Herrmann
2012-12-02 19:13         ` Marek Vasut
2012-12-02 19:39           ` Wolfgang Denk
2012-12-02 18:34       ` Pavel Herrmann
2012-12-02 19:15         ` Marek Vasut [this message]
2012-12-02 19:36 ` Wolfgang Denk
2012-12-03  3:57   ` Marek Vasut
2012-12-03 12:26     ` Wolfgang Denk
2012-12-03 14:36       ` Marek Vasut
     [not found] <CAHLo1HsRKfyWhXoEDY4wBZCCjMRQVmhXa2aq3RFx2qQh3M+ZFg@mail.gmail.com>
2013-01-13 20:54 ` Marek Vasut

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=201212022015.01618.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.