[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Todd Denniston
Subject: Re: RCS->$CVSROOT/foo
Date: Mon, 24 Oct 2005 10:35:16 -0500

bill pursell wrote:
> I've recently been linking RCS to the CVS directory containing the rcs
> files in my working directory in order to simplify the usage of a
> vimscript that displays the differences between the current file and a
> previous revision, eg:
> % ln -s $(cat CVS/Root)/$(basename $(pwd)) RCS
> This is working well, and allows make to access the RCS files directly
> as well (does make know how to find rcs files from a CVS working
> directory?)

What does this vimscript do? i.e. why can you not replace `rcsdiff` with
`cvs diff` in the script and get the same output?

> I started thinking; if for a given working directory, I can guarantee
> that I am the only developer working on the files, will it be safe to
> just use rcs directly?  In other words, if I modify files and use ci -l
> like usual, and then remove the locks when I'm done (or maybe just set
> locking to non-strict and use ci -u), will there be any undesirable
> administrative effects on the CVS repository?  If I choose the second
> option of making the files have non-strict locking, will I have to make
> them strict again before I can allow other developers access to the cvs
> repository?
your history file will not have all the data in it (which is only a minor
inconvenience), you have to always remember to take care of the strict
locking problem and if  CVS is using a different lock scheme ( like lockdir)
you could be corrupting the data as someone else does their work. There are
probably other things, but those came to me in ~5 seconds.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]