[cvsnt] Expanded quesion about commit sequencing...

Tue May 27 13:28:23 BST 2003

I think it depends on how the commit is done:
1) cvs commit  (from inside a sandbox without specifically telling which files)
2) cvs commit file1 file2 file3
3) cvs commit file1 folder/file2 file3

In case 1 the loginfo script fires once per module processed. The cvs server finds
out which files are changed in each module (folder) and processes them all in one go
per folder. Cvs will recurse down the folder tree to see if it can find changed files
that need to be committed.

In case 2 I am not sure if cvs is smart enough to see that they are all from one and
the same folder and thus can be handled in one session. But if so then it will be the
same as in case 1.  Here cvs will only commit these listed files.

In case 3 you will definitely get one trigger for each file because the folder changes
for each one.

What method TortoiseCVS uses I have no knowledge of since I don't use it....

/Bo

-----Original Message-----
From: Dave Andrus [mailto:hoopdogz at hotmail.com]
Sent: den 27 maj 2003 14:12
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Expanded quesion about commit sequencing...

Scenario:

A single developer (using Tortoise CVS) commits the following files:

  a.html
  b.html
  c.html

Scenario Question:  

At what point does CVSNT execute the script in LOGINFO?
  - After each file is committed?
  - After the session (all the files) are committed?

Problem:

I have a script that checks out modules to a website and it pauses for the
recommended 5 seconds.  For some reason though, some files (some times)
retain locks; and, I haven't been able to isolate why.  This isn't related
to realtime virus protection.

_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs