[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: locking solved

From: Tobias Brox
Subject: Re: locking solved
Date: Fri, 5 Oct 2001 00:51:53 +0400
User-agent: Mutt/1.0.1i

[raptor - Thu at 03:27:25PM +0200]
>  Why so much trouble ?
>  This will fire too much standalone/outside cvs-updates,
>  don't know which is worst. One-big or many-small!!

If there is a lot of directories, and many of them are updated on every
commit, running one "cvs update" is probably preferable instead of starting
up a lot of instances of cvs.

At the other hand, if the repository is huge, and only some few
files/directories are changed for each commit, it will proably make sense to
tell cvs exactly what to update.  That is, start one instance of the update
script for each directory.

It seems a bit strange to me that it should be so much trouble.  The loginfo
capabilities in CVS could have been designed a bit more elegant.

Unemployed hacker
Will program for food!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]