Re: CVS commit: gnusrc/gnu/dist/autoconf

[James Chacon <jchacon%genuity.net@localhost>]

And full CVS history is still there. Resurrecting files isn't a huge deal.

James


>On Wed, 14 Nov 2001, Jim Wise wrote:
>
>: Is this really the right thing to do?
>:
>: I've often been concerned that a.) removing large numbers of files from
>: dist/ dubdirectories makes for a bunch of extra work when importing the
>: next version of a package, and that b.) doing so makes for very odd cvs
>: histories if we decide we do want to use those files later -- suppose
>: that we add a flag to autoconf, and want to update the .info
>: documentation -- will we re-add the .texi files at that date?
>
>This is in the interest of keeping the in-tree copy of autoconf at a minimum
>level.  It is not built by default, and will be used to generate exactly one
>file by toolchain maintainers:  src/tools/compat/configure.
>
>If we feel at some point in the future that this copy of autoconf will have
>an expanded role (and I hope not, actually), the .texi files can be re-added
>then.
>
>-- 
>-- Todd Vierling <tv%wasabisystems.com@localhost>  *  Wasabi & NetBSD:  Run 
>with it.
>-- CDs, Integration, Embedding, Support -- http://www.wasabisystems.com/
>
>
>
>
>