Larry, Suppose my dir structure looks like this and the file that I have changed and I want to commit is file_i_changed
a/ b/ file_i_changed c/ I now cd to the directiory 'a' and run cvs ci. Assuming that all other files in other directories are up-to-date and the only file that would be committed is file_i_canged then does cvs also count 'c' as a directory that is going to be committed, or is it just '' Thanks Shubho -----Original Message----- From: Larry Jones <[EMAIL PROTECTED]> To: raptor <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Wednesday, October 03, 2001 11:19 PM Subject: Re: Locks, pls help >raptor writes: >> >> But the main questions stays : >> WHAT is the reason to hold the lock when the commit is successful at the >> time of log-info ? There should be some reason, aren't it ? :") > >The way commit currently works is that it locks *all* of the directories >that are going to be committed and runs the commitinfo script for each >directory. If none of the commitinfo scipts veto the commit, then it >goes ahead and, for each directory, does the commit and invokes the >loginfo script. When the entire commit is complete, it unlocks all of >the directories. While it would be possible to unlock each directory as >it's committed, it would be much more complicated and there doesn't seem >to be any real benefit. > >-Larry Jones > >Buddy, if you think I'm even going to BE here, you're crazy! -- Calvin > >_______________________________________________ >Info-cvs mailing list >[EMAIL PROTECTED] >http://mail.gnu.org/mailman/listinfo/info-cvs > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs