This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: An excessive commit - check recent changes to alocal, configure, all any and count
- From: Paul Brook <paul at codesourcery dot com>
- To: fortran at gcc dot gnu dot org
- Cc: "Paul Thomas" <paulthomas2 at wanadoo dot fr>,"patch" <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 30 Apr 2005 20:19:15 +0100
- Subject: Re: An excessive commit - check recent changes to alocal, configure, all any and count
- References: <001301c54db6$34db2190$0400000a@Paul>
On Saturday 30 April 2005 19:55, Paul Thomas wrote:
> In attempting to commit the matmul patch to libfortran and the
> corresponding testcase a few minutes ago, I seem to have screwed up:
>
> In spite of updating and diffing before committing, I have done something
> to alocal.m4, configure, all, any and count.
>
> I have no idea at all of what happened and apologise profusely.
You should always check the list of files that CVS says it's going to change
before proceeding. In this case it looks like the all, any and count whoever
checked in a previous patch didn't regenerate all the files properly.
The configure/aclocal changes are because you used a slightly different
version of autoconf, and shouldn't have been removed before applying.
Also, you should use the ChangeLog entry as the commit log message.
Paul