[Top][All Lists]

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

Re: CVS bashing?

From: Paul Sander
Subject: Re: CVS bashing?
Date: Thu, 12 Apr 2001 01:12:12 -0700

--- Forwarded mail from address@hidden

>On Wed, Apr 11, 2001 at 05:21:26PM -0700, Paul Sander wrote:

>> - The *info files accept a comprehensive list of sources on their command
>>   lines, limiting their scalability.  (After a branch merge on a very large
>>   project, the command line buffer of the shell invoking the *info file
>>   can overflow, causing breakage.)

>I thought all of the *info files worked on subdirectory level only.  You
>have enough files in a single directory to cause an overflow?  :->

>This sounds like it could be somewhat easy to fix.  Do something xargish
>inside of cvs to call them multiple times.

Then you have multiple invocations of the trigger script.  It's better
to use a pipe instead and pass the necessary file list through it.
This is a simple but fundamental change to the CVS design.

>> - The history file grows without bound, and can't be managed in any natural
>>   way.

>A logrotate type of program can't work against history?

It could be done, but you lose the ability to use CVS to read the result.

--- End of forwarded message from address@hidden

reply via email to

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