What Martin says is true. I was viewing the world from my narrow
perspective of the stable release, where I'm the only person to make
commits. I was confusing the role of Release Engineer with the person
who runs 'cvs commit', because I wear both hats.
BTW, for those of you running autoconf, I believe we have agreed on
version 2.13.
David, I have tried out your patch on my linux box and it didn't seem
to break anything. If Martin blesses the patch, I'll put it in
21.1.15.
- vin
Martin Buchholz <martin(a)xemacs.org> writes:
>>>>> "Vin" == vinnie shelton
<vinnie_shelton(a)notes.teradyne.com> writes:
Vin> configure.in. The Release Engineer re-generates configure.
Although, the patch creator certainly needs to run autoconf to create
a new configure script, in order to _test_ the changes.
And whoever does the `cvs commit' should commit both configure.in and
configure.
The release engineer makes sure that configure is not out of date at
release time, but this is not something that committers should rely upon.
Martin