From: Pedro Alves <palves@redhat.com>
To: musl@lists.openwall.com
Cc: Pedro Alves <palves@redhat.com>
Subject: Re: printf POSIX compliance
Date: Mon, 11 Jun 2012 10:37:06 +0100 [thread overview]
Message-ID: <4FD5BC42.2090205@redhat.com> (raw)
(Escuse me for breaking the threading, but I can't find the message's
ids from the mailing list archive.)
> Apr 19 17:43:04 <brobecke> wow, that gnulib thing is a lot more
> effort than I thought. Gotta send big thanks to palves for doing it.
> Apr 19 17:44:17 <tromey> one reason we should maybe update gnulib
> more frequently is that if we wait too long, it is harder to do
> Apr 19 17:44:36 <palves> I had no idea when I started either :-P
>
> [... 5 hours later ...]
>
> Apr 19 22:45:35 <palves> yay, gnulib patch in, I can finally
> start my week's plan :-D
Wow, way to pull things out of context to spread some silly FUD. First, you have
no idea what I had been up to those 5 hours, let alone if I was parked in
front of the computer the whole time... Then, the "patch" was really a
multitude of patches, involving fixes to issues in GDB and GDBserver (GDBserver was
not using gnulib before, and that was that prompted the gnulib update), with the
most time consuming bit being that the way that GDB imports gnulib was changed
dramatically, because we now have _two_ programs in the same tree that share
the _same_ gnulib import in a way no other program does, afaik.
http://sourceware.org/ml/gdb-patches/2012-04/msg00426.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00556.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00558.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00608.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00609.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00618.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00620.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00622.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00627.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00631.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00637.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00646.html
http://sourceware.org/ml/gdb-patches/2012-04/msg00692.html
As Reuben says, just updating gnulib is a trivial case of git
pull + running gnulib-tool.
--
Pedro Alves
next reply other threads:[~2012-06-11 9:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 9:37 Pedro Alves [this message]
2012-06-11 12:28 ` Luca Barbato
2012-06-11 13:31 ` Rich Felker
-- strict thread matches above, loose matches on Subject: below --
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
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
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=4FD5BC42.2090205@redhat.com \
--to=palves@redhat.com \
--cc=musl@lists.openwall.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.
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).