This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: submitting patches to configure.in -- include results of aclocal/autoconf/autoheader/automake?
- From: DJ Delorie <dj at redhat dot com>
- To: gcc at lists dot megacz dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 10 Dec 2001 15:32:08 -0500
- Subject: Re: submitting patches to configure.in -- include results of aclocal/autoconf/autoheader/automake?
- References: <86bsh7iwd0.fsf@megacz.com>
> When submitting a patch to a configure.in file, should the submitter
> include diffs of the changes to other files (Makefile.in, etc), or
> will the maintiner who commits it to cvs re-run
> aclocal/autoconf/autoheader/automake before doing a cvs commit?
When you post a patch to the mailing lists for approval, IMHO you
don't need to include diffs for the regenerated files. The reviewer
can regenerate them if they really want to know what the changes are.
However, *you* should look at those diffs, to make sure that you
aren't accidentally using the wrong version of the tools and thus are
causing unexpected unrelated changes to the generated files.
Of course, whoever checks in the .in files (you or the maintainer)
must check in freshly regenerated files that go along with it also.