> | > In fact, I realized that latter on, and changed that, but I suppose
> | > the mere presence of Autoconf (now renamed Autom4te) on the CVS repo
> |
> | Actually, no you didn't - the problem is that it still has files in it
> | (otherwise cvs update -dP would have pruned it).
>
> :-)=)
>
> Ahe
| > In fact, I realized that latter on, and changed that, but I suppose
| > the mere presence of Autoconf (now renamed Autom4te) on the CVS repo
|
| Actually, no you didn't - the problem is that it still has files in it
| (otherwise cvs update -dP would have pruned it).
|
| $ cd lib
| $ cvs upd
> In fact, I realized that latter on, and changed that, but I suppose
> the mere presence of Autoconf (now renamed Autom4te) on the CVS repo
Actually, no you didn't - the problem is that it still has files in it
(otherwise cvs update -dP would have pruned it).
$ cd lib
$ cvs update -d Autoconf
c
On Wed, Aug 08, 2001 at 06:43:00PM +0200, Tim Van Holder wrote:
> I should have noticed this earlier, but it's been a while
> since I last updated the CVS tree.
> I just updated it and ran into an annoying problem: there is both a
> lib/Autoconf and a lib/autoconf directory. This is not possible o
