From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: glibc LC_COLLATE bug
Date: Sun, 16 Nov 2008 16:23:06 +0100 [thread overview]
Message-ID: <gfpdsq$6vm$2@ger.gmane.org> (raw)
In-Reply-To: <1226842838.4912.13.camel@utx.utx.cz>
On 16-11-08 14:40, Stanislav Brabec wrote:
> Stanislav Brabec wrote:
>> Graeme Gregory wrote:
>>> On Tue, 2008-11-11 at 20:55 +0100, Stanislav Brabec wrote:
>>>
>>>> 3) Add new versions to preferred-om-2008-versions.inc
>>>>
>>> As claws maintainer and OM person please do this version.
>> Well, I naively expected that the latest version will work better.
>
> Updated in OE. claws-mail-3.6.1 should now build and work.
Could split such changes up in more commits in the future? Anyway, nice
work!
regards,
Koen
prev parent reply other threads:[~2008-11-16 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 19:55 openmoko OE devs: update claws-mail and libetpan? Stanislav Brabec
2008-11-11 22:29 ` Graeme Gregory
2008-11-12 7:35 ` Stanislav Brabec
2008-11-16 13:40 ` glibc LC_COLLATE bug (was: openmoko OE devs: update claws-mail and libetpan?) Stanislav Brabec
2008-11-16 15:23 ` Koen Kooi [this message]
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='gfpdsq$6vm$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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