Re: Locks, pls help

2001-10-04 Thread Larry Jones
Shubhabrata Sengupta writes: > > 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 othe

Re: Locks, pls help

2001-10-03 Thread Shubhabrata Sengupta
AIL 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 suc

Re: Locks, pls help

2001-10-03 Thread Larry Jones
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 a

Re: Locks, pls help

2001-10-03 Thread raptor
| > I'm tring a loginfo-script.. and I got lock problems.. | [snip] | > I've read in the manual but the explanation of the LOCKS is too 'blury' .. | | PEBKAC? ]- what this mean !!! | > First of all I have to create #cvs.lock dir, | | Why? | | Have you read the manual section on loginfo? | http://

Re: Locks, pls help

2001-10-02 Thread Tobias Brox
[raptor - Tue at 07:11:06PM +0200] > hi, > > I'm tring a loginfo-script.. and I got lock problems.. Been there, done that. It seems like the commit-lock is removed only after the loginfo-script has returned. It doesn't make sense to me? I simply forked the loginfo-script, and there were no pr

Re: Locks, pls help

2001-10-02 Thread Larry Jones
raptor writes: > > I'm tring a loginfo-script.. and I got lock problems.. http://www.cvshome.org/docs/manual/cvs_18.html#SEC171 -Larry Jones I'm writing you a message in code. How do you spell "nincompoop"? -- Calvin ___ Info-cvs mailing list [EMAI

Re: Locks, pls help

2001-10-02 Thread Matt Riechers
raptor wrote: > > hi, > > I'm tring a loginfo-script.. and I got lock problems.. [snip] > I've read in the manual but the explanation of the LOCKS is too 'blury' .. PEBKAC? > First of all I have to create #cvs.lock dir, Why? Have you read the manual section on loginfo? http://www.cvshome.org

Re: Locks, pls help

2001-10-02 Thread David Everly
If I understand what you are trying to do, prehaps this will answer: http://www.cvshome.org/docs/manual/cvs_18.html#SEC171 On Tue, Oct 02, 2001 at 07:11:06PM +0200, raptor wrote: > hi, > > I'm tring a loginfo-script.. and I got lock problems.. > OK first I expected that 'cause the cvs-commit is

Locks, pls help

2001-10-02 Thread raptor
hi, I'm tring a loginfo-script.. and I got lock problems.. OK first I expected that 'cause the cvs-commit is already finished at log-info-stage all locks should be already released so I can switch to my working directory and update it (read) but I have zero success and had to go to Repositor