From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Cc: rrt@sc3d.org
Subject: Re: printf POSIX compliance
Date: Fri, 08 Jun 2012 18:38:31 +0200 [thread overview]
Message-ID: <4FD22A87.1030709@barfooze.de> (raw)
In-Reply-To: <CAOnWdohVh21QvJW4=QtuhZOYCvt-wYdZ34pJYTwGVnTqn9eX_A@mail.gmail.com>
On 06/08/2012 06:16 PM, Reuben Thomas wrote:
>
> The maintainers (Gary Vaughan and Eric Blake) are both active, so I
> think it's worth it; Eric works on gnulib too.
>
> You're right that of course for practical purposes it requires new
> releases using the fixed version of gnulib, but many of these issues
> (this one included) affect multiple packages, and also it's possible
> to "repair" a broken package by refreshing gnulib before building.
>
i was recently following a conversation in #gdb where GNU people (!)
were trying to update gnulib and failed...
it took them about 5 hours to get everything fixed.
i don't think most users of gnulib want to go through this mess...
next prev parent reply other threads:[~2012-06-08 16:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 10:34 Reuben Thomas
2012-06-08 12:19 ` Luca Barbato
2012-06-08 12:32 ` Reuben Thomas
2012-06-08 14:04 ` Szabolcs Nagy
2012-06-08 14:16 ` Rich Felker
2012-06-08 14:44 ` Rich Felker
2012-06-08 14:55 ` Rich Felker
2012-06-08 15:06 ` Szabolcs Nagy
2012-06-08 15:29 ` Rich Felker
2012-06-08 15:43 ` Reuben Thomas
2012-06-08 15:53 ` Rich Felker
2012-06-08 16:16 ` Reuben Thomas
2012-06-08 16:38 ` John Spencer [this message]
2012-06-08 16:37 ` Reuben Thomas
2012-06-09 7:43 ` John Spencer
2012-06-09 14:17 ` Reuben Thomas
2012-06-08 16:46 ` John Spencer
2012-06-08 16:46 ` Reuben Thomas
2012-06-08 16:51 ` Rich Felker
2012-06-08 16:58 ` Reuben Thomas
2012-06-08 17:00 ` Rich Felker
2012-06-08 17:07 ` Reuben Thomas
2012-06-08 23:25 ` Rich Felker
2012-06-09 2:33 ` Isaac Dunham
2012-06-09 2:45 ` Rich Felker
2012-06-09 12:58 ` Szabolcs Nagy
2012-06-09 14:17 ` Reuben Thomas
2012-06-09 21:11 ` Rich Felker
2012-06-09 21:24 ` Reuben Thomas
2012-06-09 14:15 ` Reuben Thomas
2012-06-11 9:37 Pedro Alves
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=4FD22A87.1030709@barfooze.de \
--to=maillist-musl@barfooze.de \
--cc=musl@lists.openwall.com \
--cc=rrt@sc3d.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).