Bob Friesenhahn wrote: > Within the bounds of technical recommendations/comments made already (by > Ralf and perhaps others), I recommend that you commit your log-jammed > Cygwin patches according to the 72 hour rule. Otherwise it is unlikely > that there will be any forward progress. If anything becomes broken for > some other platform, it is certain to be fixed.
I'll take that as permission only to start the 72 hour clock for the two patches I have most recently pinged. http://lists.gnu.org/archive/html/libtool-patches/2010-02/msg00000.html http://lists.gnu.org/archive/html/libtool-patches/2010-02/msg00001.html The others (and there are about 11 in total) I will repost individually, and revisit them in sequence. I know it is difficult to review complex patches, and several of mine are that. So, I don't want to overload anybody with a flood of complex patches to review under some ticking-clock scenario. So...just these two, for now, and nobody needs to panic. Much. > Development libtool has not been released for quite a long time now > (since September 2008) and will need to undergo regression testing on a > wide variety of platforms prior to release. Yes, I'm afraid so. Even gcc is using a non-released libtool (synced with git master around 12-05-2009), so there appears to be quite some pressure for updated features/bugfixes from the outside world. Nothing like the pre-2.2.x days, tho. -- Chuck
