Re: locks; strict;

[EMAIL PROTECTED] writes: What exactly do the locks and the strict field, in the admin-section of the RCS file, tell if they were filled? Why are you asking RCS file format questions on the CVS list? I understand a lock entry would have following format: Id : num where id is

RE: Locks

Title: Locks -Original Message-From: Jasmeet Singh Virdi [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 21, 2002 7:46 AMTo: [EMAIL PROTECTED]Subject: Locks Hi all, ne pointer on how to impliment LOCKS in CVS for NT server on a win2K box, with only windows

Re: Locks

[ On Thursday, February 21, 2002 at 19:15:45 (+0530), Jasmeet Singh Virdi wrote: ] Subject: Locks ne pointer on how to impliment LOCKS in CVS for NT server on a win2K box, with only windows clients. First of all you probably cannot do what you want with CVS. CVS is not designed to

Re: Locks

--- Greg A. Woods [EMAIL PROTECTED] wrote: [ On Thursday, February 21, 2002 at 19:15:45 (+0530), Jasmeet Singh Virdi wrote: ] ne pointer on how to impliment LOCKS in CVS for NT server on a win2K box, with only windows clients. First of all you probably cannot do what you want with

Re: Locks, pls help

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

Re: Locks, pls help

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 other

Re: Locks, pls help

| 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? |

Re: Locks continued...

[raptor - Wed at 12:36:34PM +0200] 1. CVS walks and see test1 and test2 has to be commited 'cause they are changed 2. test1 and test2 are commited 3. CVS call log-info script 4. log-info is started and it forks process to do the main-working copy update 5. Meanwhile CVS continues to

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

Re: Locks, pls help

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

Re: Locks, pls help

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?

Re: Locks, pls help

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 [EMAIL

Re: Locks, pls help

[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