Subject: Re: Speedy CVS Updates
To: dieter <dieter.NetBSD@pandora.be>
From: Greg A. Woods <email@example.com>
Date: 10/11/2004 12:00:21
[ On Saturday, October 9, 2004 at 10:46:11 (+0000), dieter wrote: ]
> Subject: Speedy CVS Updates
> The idea is that it's silly to crawl through the whole tree when in fact
> only a few files changed and it is known which files and in what way they
> changed. (It is known because all the information needed is mailed to
> -changes mailing lists.) First I let procmail pipe these mails through a
> perl script which creates logfiles. SCU downloads these logfiles to
> determine what needs to be updated.
Note that CVSup will sort of do the same thing, but in a more general
way. It won't be nearly so fast as your script could be, but it avoids
the lock-step nature of a remote "cvs update".
Of course it requires support on the server side, particularly for the
case where it's replacing the functionality of a "cvs update".
Greg A. Woods
+1 416 218-0098 VE3TCP RoboHack <firstname.lastname@example.org>
Planix, Inc. <email@example.com> Secrets of the Weird <firstname.lastname@example.org>