Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Mon, 11 Jun 2012 10:37:06 +0100
From: Pedro Alves <>
CC: Pedro Alves <>
Subject: Re: printf POSIX compliance

(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.

As Reuben says, just updating gnulib is a trivial case of git
pull + running gnulib-tool.

Pedro Alves

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.