Re: coreutils failure on Mac OS X 10.5

Can someone give more clear instruction to apply the patch? I copy the following patch text into patch.txt file and then I run patch -p0 < patch.txt What I get is the following error message: patch unexpectedly ends in middle of line patch: Only garbage was found in the patch input. If so

Re: Updated INSTALL from Autoconf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Karl Berry on 8/22/2008 7:10 PM: > Karl, do you have a cron job for grabbing upstream changes from Autoconf > to gnulib's doc/INSTALL? > > Yes, there is supposed to be. I think it wasn't showing up because once > again the sour

Re: snapshot in preparation for m4 1.4.12

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 8/19/2008 6:50 AM: > >> SKIP: test-lock >> SKIP: test-tls > > Expected; these tests are only run if you use ./configure --enable-threads > (generally overkill for m4, since it does not need threading). Bruno, can > I apply

Re: Updated INSTALL from Autoconf

Karl, do you have a cron job for grabbing upstream changes from Autoconf to gnulib's doc/INSTALL? Yes, there is supposed to be. I think it wasn't showing up because once again the source project changed to git and I didn't know. I'll fix that, meanwhile, feel free to push the new INSTA

Updated INSTALL from Autoconf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karl, do you have a cron job for grabbing upstream changes from Autoconf to gnulib's doc/INSTALL? There were two recent patches in Autoconf that would be nice to have: - -- Don't work too hard, make some time for fun as well! Eric Blake

Re: `count-one-bits' -> LGPLv2+

Hi, Eric Blake <[EMAIL PROTECTED]> writes: > As author, you are entitled to make that change. And I agree that > count-one-bits is library quality (since it can often be a thin wrapper > around a special assembly instruction). So I went ahead and pushed this > commit: Thanks! Ludo'.

Re: `count-one-bits' -> LGPLv2+

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ben Pfaff on 8/22/2008 9:56 AM: > [EMAIL PROTECTED] (Ludovic Courtès) writes: > >> Would you be OK to relicense `count-one-bits' under LGPLv2+ for use in >> Guile 1.9 (aka. the development branch)? > > I don't know who gets to make these

Re: gl_FUNC_OBSTACK_PRINTF_POSIX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Andreas Schwab on 8/22/2008 1:29 PM: > Eric Blake <[EMAIL PROTECTED]> writes: > >> Please apply; that should count as obvious. > > Sorry, I don't have write access. OK, done. You've made quite a few gnulib contributions; it's time to t

Re: gl_FUNC_OBSTACK_PRINTF_POSIX

Eric Blake <[EMAIL PROTECTED]> writes: > Please apply; that should count as obvious. Sorry, I don't have write access. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D

Re: gl_FUNC_OBSTACK_PRINTF_POSIX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Andreas Schwab on 8/22/2008 10:40 AM: > 2008-08-22 Andreas Schwab <[EMAIL PROTECTED]> > > * m4/obstack-printf-posix.m4 (gl_FUNC_OBSTACK_PRINTF_POSIX): > Remove spurious space in assignment. Please apply; that should count a

gl_FUNC_OBSTACK_PRINTF_POSIX

2008-08-22 Andreas Schwab <[EMAIL PROTECTED]> * m4/obstack-printf-posix.m4 (gl_FUNC_OBSTACK_PRINTF_POSIX): Remove spurious space in assignment. diff --git a/m4/obstack-printf-posix.m4 b/m4/obstack-printf-posix.m4 index 5fa740f..8768e67 100644 --- a/m4/obstack-printf-posix.m4 +++

Re: `count-one-bits' -> LGPLv2+

[EMAIL PROTECTED] (Ludovic Courtès) writes: > Would you be OK to relicense `count-one-bits' under LGPLv2+ for use in > Guile 1.9 (aka. the development branch)? I don't know who gets to make these decisions, but as the module's maintainer I'm fine with that. -- Ben Pfaff http://benpfaff.org

`count-one-bits' -> LGPLv2+

Hi, Would you be OK to relicense `count-one-bits' under LGPLv2+ for use in Guile 1.9 (aka. the development branch)? Thanks, Ludovic.