[cvsnt] Commit sequence?

Bo Berglund bo.berglund at telia.com
Sun May 25 09:57:11 BST 2003


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Tony,
I have an observation/question regarding the CVSNT handling for
commits where the user has been working in flat mode in WinCvs and
selected files from several directories:
It looks like CVSNT is *not* checking the list of files received from
WinCvs such that it sorts them in module order before processing. This
leads to many invocations of the loginfo scripts and indicates that
cvs is running many processes when it could have sufficed with fewer.
Example:
Files committed from WinCvs in flat view with sorting by file name in
the file view. Files are named alphabetically:
source/Afile.c
common/Bfile.c
source/Cfile.c
common/Dfile.c
source/Efile.c
common/Ffile.c
etc (you get the picture, right?)

Now this seems to lead to at least 6 runs of cvs on the server, one
for each single file where it should have been possible to collect the
list into memory, sort by module and then starting cvs only twice
(once for each module).

Is this by design or by oversight?
Seems like a waste of processing on the server to start a new process
for basically each single file when it would *not* have been
necessary...



/Bo
(Bo Berglund, developer in Sweden)


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook