Benjamin Kosnik <[EMAIL PROTECTED]> writes:
> > Could we modify the CVS commit filters to *require* the right
> > versions? If it detects a commit with the wrong version (at least,
> > assuming the old rev had the right version), it can just reject it.
>
> Dunno if this is possible, but this wou
> "KC" == Kelley Cook <[EMAIL PROTECTED]> writes:
KC> Unfortunately, we have automake 1.9.3, 1.9.4 and 1.9.5 floating
KC> throughout the tree. I propose standardizing the entire tree on 1.9.6,
KC> as it is the current release; moreover the 1.9 branch has only had a
KC> few minor patches since
> Could we modify the CVS commit filters to *require* the right
> versions? If it detects a commit with the wrong version (at least,
> assuming the old rev had the right version), it can just reject it.
Dunno if this is possible, but this would be great. It would be nice if
there was a way to se
> Thanks Tom for pointing this out. We have to all keep these
> autotools versions synced: it bugs everybody to have extraneous
> differences in trees due to version mis-match.
Could we modify the CVS commit filters to *require* the right
versions? If it detects a commit with the wrong version (
Thanks Tom for pointing this out. We have to all keep these autotools
versions synced: it bugs everybody to have extraneous differences in
trees due to version mis-match.
>Unfortunately, we have automake 1.9.3, 1.9.4 and 1.9.5 floating
>throughout the tree.
How did this happen?
>I propose sta
--- Tom Tromey <[EMAIL PROTECTED]> wrote:
> > "KC" == Kelley Cook <[EMAIL PROTECTED]> writes:
>
> KC> 2005-08-19 Kelley Cook <[EMAIL PROTECTED]>
> KC> * Makefile.am (ACLOCAL_AMFLAGS): Also include "..".
> KC> * acinclude.m4: Delete. Extract CHECK_FOR_BROKEN_MINGW_LD to
> ...
> KC> * m
