-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI: I committed a patch that kills the trailing whitespace in argz.{c,m4}
to match gnulib's change:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=a0bdb06#patch10
Also, would anyone be interested in a patch that renames argz_.h to
.
+
Resynchronize argz whitespace changes from gnulib.
* libltdl/m4/argz.m4: Kill trailing whitespace.
* libltdl/argz.c: Likewise.
diff --git a/Makefile.am b/Makefile.am
index 0085c7f..003f9d9 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -357,8 +357,8 @@ ltdldatafiles = libltdl
On Tue, 20 May 2008, Eric Blake wrote:
Also, would anyone be interested in a patch that renames argz_.h to
argz.in.h to match gnulib? Gnulib recently changed to avoid _ in file
names where possible, and these days, platforms that don't handle two . in
a file name are generally not worth porting
On Tue, 20 May 2008, Eric Blake wrote:
According to Eric Blake on 5/20/2008 6:32 AM:
| Also, would anyone be interested in a patch that renames argz_.h to
| argz.in.h to match gnulib? Gnulib recently changed to avoid _ in file
| names where possible, and these days, platforms that don't handle
On Tue, 20 May 2008, Bob Friesenhahn wrote:
There is a palpable cost to renaming libltdl/argz_.h and the cost should be
carefully considered before renaming files. Have you considered the cost?
What is the value behind this change and is the value obtained greater than
the cumulative cost?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bob Friesenhahn on 5/20/2008 10:14 AM:
| On Tue, 20 May 2008, Eric Blake wrote:
| Also, would anyone be interested in a patch that renames argz_.h to
| argz.in.h to match gnulib? Gnulib recently changed to avoid _ in file
| names where
On Tue, 20 May 2008, Eric Blake wrote:
| What qualifies a platform as not being worth porting to?
It's somewhat subjective. The gnulib mailing list has come up with an
ad-hoc definition of any platform released within the last 3-5 years, and
preferably where the vendor has not declared the
