Re: reserved checkout

2002-02-08 Thread Matthias Kienle

I tried the patches available at SourceForge/RCVS and compiled / installed the 
cvs. It looks good in the first instance. Hope the users of the binary file see 
it so too.
Developers be able to do further on concurrent code writing without using the 
-c option. Is that true? I tested with some configuration files and feel me 
lucky without using the -c option.

Thanks
Matthias

 Have you tried the patches available at
 SourceForge/RCVS?
 
 If so, your development process should include the
 following:
 1. Developers put edit -c in ~/.cvsrc.
 2. Developers cvs edit file(s).
 3. If the edit aborts (due to other editors),
 developer communicates with others.
 4. Developers proceed only if there's no danger of
 future merges.
 
 Note that this won't alleviate the problem of
 concurrent development through branches.
 
 Noel
 --- Matthias Kienle
 [EMAIL PROTECTED] wrote:
   [ On Thursday, January 31, 2002 at 10:34:52
  (+0100), Matthias Kienle
   wrote: ]
Subject: reserved checkout
   
What do I wrong?
   
   Don't use reserved checkouts with CVS -- CVS is
  the Concurrent Versions
   System!
   
  
  I know cvs is a concurrent version system, but a new
  requirement comes up in 
  our department to use in future only one version
  system. The other version 
  system administrated binary files like word, excel
  and powerpoint. CVS (and 
  other version systems too) can not merge binary
  files after more than one edit 
  from several editors of the same version. The other
  version system can do 
  reserved checkouts but it runs on a windows server
  and has no command line.
  
  In a first test we used the editors and watcher
  function of cvs, but the test 
  shows us it is not enough. I must often merge by
  hand two versions and I can 
  say I hate it.
  
  I am a linuxer and I would hate it to explain my
  manager that cvs does not 
  support reserved checkouts for binary files. I
  control all web pages, server 
  configuartions and the total source code in a cvs
  repository. I love my command 
  line for cvs and I love my CVS.
  
  I know I am sitting between two chairs.
  
  Matthias
  


-
This mail sent through IMP: webmail.fht-esslingen.de

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



Re: reserved checkout

2002-02-01 Thread Matthias Kienle

 [ On Thursday, January 31, 2002 at 10:34:52 (+0100), Matthias Kienle
 wrote: ]
  Subject: reserved checkout
 
  What do I wrong?
 
 Don't use reserved checkouts with CVS -- CVS is the Concurrent Versions
 System!
 

I know cvs is a concurrent version system, but a new requirement comes up in 
our department to use in future only one version system. The other version 
system administrated binary files like word, excel and powerpoint. CVS (and 
other version systems too) can not merge binary files after more than one edit 
from several editors of the same version. The other version system can do 
reserved checkouts but it runs on a windows server and has no command line.

In a first test we used the editors and watcher function of cvs, but the test 
shows us it is not enough. I must often merge by hand two versions and I can 
say I hate it.

I am a linuxer and I would hate it to explain my manager that cvs does not 
support reserved checkouts for binary files. I control all web pages, server 
configuartions and the total source code in a cvs repository. I love my command 
line for cvs and I love my CVS.

I know I am sitting between two chairs.

Matthias

-
This mail sent through IMP: webmail.fht-esslingen.de

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



reserved checkout

2002-01-31 Thread Matthias Kienle

Hello,

I am a beginner with reserved checkout. I found several helpentries on
the cvshome page and want test a method using the rcslock file. I added
a line in the commitinfo file like the follow:

ALL /usr/lib/cvs/contrib/rcslock

If user A locks and edit a file out of the repository subsequently an
other user edit the file. User B commit first the file and should
receive an error but the commit ends successfully. I activated strict
locking for the cvs repository.

What do I wrong?

Matthias


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs