Re: [PATCH] Add new 'AM_PROG_AR' macro, triggering the 'ar-lib' script.

On Tuesday 14 September 2010, Peter Rosin wrote: > Hi Stefano, > > Den 2010-09-14 20:14 skrev Stefano Lattarini: > > On Tuesday 14 September 2010, Peter Rosin wrote: > [CUT] > >> or otherwise difficult to merge due to other changes. I'm also > >> not sure if this is the desired route. Please advis

Re: [PATCH] Add new 'AM_PROG_AR' macro, triggering the 'ar-lib' script.

Hi Stefano, Den 2010-09-14 20:14 skrev Stefano Lattarini: > On Tuesday 14 September 2010, Peter Rosin wrote: >> Hi! > Hello Peter. Hope you don't mind a quick partial review until we > hear from Ralf... Not at all, he's got enough to do as it is I would think... >> This is a second attempt to i

[SIMPLE PATCH] {maint} Fixlets for HACKING.

OK for maint? Regards, Stefano From 158f31906d728c75d78272a00f352857c81931a2 Mon Sep 17 00:00:00 2001 From: Stefano Lattarini Date: Tue, 14 Sep 2010 22:50:15 +0200 Subject: [PATCH] Fixlets for HACKING. * HACKING (Administrivia): Fixed typo `NES' for `NEWS'. (Naming): Do not refer to a conven

[SIMPLE PATCH] {maint} Make HACKING visible to the end user (was: Mentioning HACKING in ChangeLog)

Since I see no reason forcing us to keep the HACKING file "invisible" to the end user (not in ChangeLog, not in distributed tarball, ...), I've gone ahead and written a very simple patch to mke it "visible". OK for maint? Regards, Stefano From 1ef59cdc330f2e863fcd4d9d2a6fb712826ffeb2 Mon Sep 17

[SIMPLE PATCH] {maint} tests/README: Tell not to put `gzip' in $required.

OK to push to maint? --- ChangeLog|4 tests/README |3 ++- 2 files changed, 6 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog index 7b64d55..286c0be 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2010-09-14 Stefano Lattarini + + * tests/README:

Mentioning HACKING in ChangeLog (was: Re: [FYI] Fix regression in test `colon4.test'.)

Hi Ralf. On Monday 13 September 2010, Ralf Wildenhues wrote: > > I'm pushing this to maint. > > > * HACKING: Hint at old commits with `git describe' output. > > diff --git a/HACKING b/HACKING > index d9b2099..ecbd0a8 100644 > --- a/HACKING > +++ b/HACKING > @@ -143,6 +143,8 @@ > the activ

Re: [PATCH] Add new 'AM_PROG_AR' macro, triggering the 'ar-lib' script.

On Tuesday 14 September 2010, Peter Rosin wrote: > Hi! Hello Peter. Hope you don't mind a quick partial review until we hear from Ralf... > This is a second attempt to implement AM_PROG_AR. The previous > attempt was bundled with the addition of the 'ar-lib' script but > was left behind. I have n

[PATCH] Add new 'AM_PROG_AR' macro, triggering the 'ar-lib' script.

Hi! This is a second attempt to implement AM_PROG_AR. The previous attempt was bundled with the addition of the 'ar-lib' script but was left behind. I have now fleshed it out with tests and portability warnings etc. I think I have everything in the thread covered: http://lists.gnu.org/archive/htm

Re: [PATCH] Overhauled and modularized tests in `instspc.test'.

And by the way, the patch can still be simplified by noting that simple whitespace characters do not create problems at make-time test generation; so I'd like to squash in the following. OK? Regards, Stefano -*-*-*- diff --git a/tests/gen-instspc-tests b/tests/gen-instspc-tests index 4b9cc46

Re: [PATCH] Overhauled and modularized tests in `instspc.test'.

On Monday 13 September 2010, Ralf Wildenhues wrote: > Hi Stefano, > > > > > OK for master? > > This patch ought to be tested with AIX sh, Tru64 ksh, and IRIX. > When you're through addressing the nits below, and still don't have > access, ping me and I'll test it. Thanks for the offer! In fact,

[FYI] {master} Prefer `$(am__cd)' to plain `cd' in our Makefiles.

I pushed the attached patch (pre-approved by Ralf) to master. Regards, Stefano -*-*- Prefer `$(am__cd)' to plain `cd' in our Makefiles. * Makefile.am (recheck, dist-hook, git-dist, path-check, fetch) (release-stats): Use `$(am__cd)' rather than plain `cd'. * tests/Makefile.am ($(srcdir)/para