Re: FYI: more updated files

[Ralf Wildenhues]

Hi Paul,

* Paul Eggert wrote on Sun, Apr 09, 2006 at 09:07:00PM CEST:
> Ralf Wildenhues <address@hidden> writes:
> 
> >> Perhaps all these files should be synced as part of 'bootstrap'?
> >
> > Well, the release procedure updates them all automatically.  I was doing
> > it manually because I went and fixed some stuff upstream as well.  So
> > when that standards.texi change is in, I'll sync the rest.  OK?
> 
> syncing is good, yes.  But if 'bootstrap' does it, then we don't have
> to worry so much about last-minute glitches in the release procedure.

First, we don't have a `bootstrap' script right now.  Second, I see no
issues that make this worry particularly true at the moment; my fixing
upstream is only trivial nits.  Third, how about just this.

You could argue that committers may not read `HACKING', as they don't
regenerate `configure' regularly.  Well, here's a social problem better
not solved by technical means.  (To keep sanity while hacking, I will
oppose any technical means to update `configure' with macro changes that
are potentially unstable.)

Cheers,
Ralf

Index: HACKING
===================================================================
RCS file: /cvsroot/autoconf/autoconf/HACKING,v
retrieving revision 1.5
diff -u -r1.5 HACKING
--- HACKING     14 May 2005 07:00:39 -0000      1.5
+++ HACKING     10 Apr 2006 11:09:07 -0000
@@ -55,6 +55,7 @@
 
 ** Update the foreign files
 Running `make update' in the top level should make it all for you.
+Use liberally.
 
 ** Update configure
 As much as possible, to try an Autoconf that uses itself.  That's