I am transitioning a team from RCS to CVS.
in some cases they just copied the ,v files to the repository. Which is fine except
when the files are locked. I know I need to do a
%cvs admin -u1.1 filename to unlock the files
How do I find all the locked file?
TIA
Sally Smart Miller
I used to
On Fri, May 17, 2002 at 11:38:08AM -0400, Miller Sally S NPRI wrote:
I am transitioning a team from RCS to CVS.
in some cases they just copied the ,v files to the repository. Which is fine except
when the files are locked.
How do I find all the locked file?
find $CVSROOT -name *,v -print
Larry Jones [EMAIL PROTECTED] wrote:
Georg Wilckens writes:
the hint. :) :) Maybe I have an misconception regarding locking... can
CVS be safely used without locking? Couldn't there be some unsuspected
merges when two people commit a file shortly after each other?
Of course CVS can
Eric Siegerman [EMAIL PROTECTED] wrote:
As others have commented, CVS was designed to be used without
locking, without screwing you up in the process.
I got the point now, thanks to all, who gave explanations! :)
Hey, that's neat. Couldn't find that in the documentation, thanks for
On Sat, Mar 09, 2002 at 12:47:16PM +0100, Georg Wilckens wrote:
What is the connection between cvs admin and
rcs? Are the command simply passed through?
Essentially (though as you've learned by now, it's no longer
implemented that way).
CVS started off as a wrapper around RCS, and a pretty
It's a syntactic fossil,
like the plural forms
Ahhh... and like VAX and VAXen.
gdr
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Hello all,
we have a project with quite a few people working on a
project. Sometimes files remain locked in CVS, because someone forgot
to remove the lock. Unfortunately the guilty is sometimes
unreachable. Is there an easy way to remove the lock? Or do I have to
edit the RCS-file and remove the
Don't lock files. Instead, try using the advisory
lock patch available at SourceForge under project
RCVS.
Noel
--- Georg Wilckens [EMAIL PROTECTED] wrote:
Hello all,
we have a project with quite a few people working on
a
project. Sometimes files remain locked in CVS,
because someone
Maybe, but that still doesn't answer his question. I actually would be
interested in people's thoughts on that as well.
Dave
-Original Message-
From: Noel Yap [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 08, 2002 8:13 AM
To: Georg Wilckens; [EMAIL PROTECTED]
Subject: Re: locked files
Georg Wilckens writes:
we have a project with quite a few people working on a
project. Sometimes files remain locked in CVS, because someone forgot
to remove the lock. Unfortunately the guilty is sometimes
unreachable. Is there an easy way to remove the lock? Or do I have to
edit the
Larry Jones [EMAIL PROTECTED] wrote:
unreachable. Is there an easy way to remove the lock? Or do I have to
edit the RCS-file and remove the lock there by hand?
As others have said, the right solution is to quit locking files, but
you can break someone else's lock with cvs admin -u,
--- Georg Wilckens [EMAIL PROTECTED] wrote:
Hey, that's neat. Couldn't find that in the
documentation, thanks for
the hint. :) :) Maybe I have an misconception
regarding locking... can
CVS be safely used without locking? Couldn't there
be some unsuspected
merges when two people commit a
Georg Wilckens writes:
Hey, that's neat. Couldn't find that in the documentation, thanks for
the hint. :) :) Maybe I have an misconception regarding locking... can
CVS be safely used without locking? Couldn't there be some unsuspected
merges when two people commit a file shortly after each
On Fri, Mar 08, 2002 at 05:33:34PM +0100, Georg Wilckens wrote:
Maybe I have an misconception regarding locking... can
CVS be safely used without locking? Couldn't there be some unsuspected
As others have commented, CVS was designed to be used without
locking, without screwing you up in the
Sasha Case writes:
We've recently moved over from plain rcs to a cvs based system. Our rcs
system was somewhat mismanaged, so long forgotten locked files keep popping
up. The problem is that the previous admin set artificial LOGNAMEs, so the
users can't unlock the files in cvs.
Yes
G'day,
We've recently moved over from plain rcs to a cvs based system. Our rcs
system was somewhat mismanaged, so long forgotten locked files keep popping
up. The problem is that the previous admin set artificial LOGNAMEs, so the
users can't unlock the files in cvs.
One solution
[EMAIL PROTECTED] on 2000.10.30 13:21:30
This topic has been discussed numerous times and I still haven't seen an
absolute need to use "cvs admin -l".
Well, some people don't trust that if someone gets a conflict when
trying to merge, that the resulting file will be OK, because of human
has been discussed numerous times and I still haven't seen an
absolute need to use "cvs admin -l".
Noel
[EMAIL PROTECTED] on 2000.10.27 18:41:49
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: locked files
I asked this question a while ago, and know I have an answer.
This topic has been discussed numerous times and I still haven't seen an
absolute need to use "cvs admin -l".
Well, some people don't trust that if someone gets a conflict when
trying to merge, that the resulting file will be OK, because of human
errors.
Locking stalls development, but
Thomas Olausson wrote:
This topic has been discussed numerous times and I still haven't seen an
absolute need to use "cvs admin -l".
Well, some people don't trust that if someone gets a conflict when
trying to merge, that the resulting file will be OK, because of human
errors.
I
this way seems like second guessing your programmers too much. By the
same
token someone could accidentally write a bug into a program even while
normally
changing it, but can you really account for it using the tool? Probably
not...code reviews should be set up to prevent bad code from getting
I asked this question a while ago, and know I have an answer.
My colleagues complained on CVS because it's hard to know which files
are locked by other people (yes we use the locking strategy).
If someone wants to know how to get this information out of CVS,
mail me.
Regards,
Thomas
e 21, 2000 7:54 PM
Subject: RE: Please help: WinCVS: Tcl script looking for locked files
Thanks very much, Lars-Christian !!
I managed to get your script to work with WinCVS.
There seems to be a bug in the internal WinCVS command used in the
original
script.
So here for all of you the Wi
Hi all,
I am looking for a Tcl script to check, if files are locked by somebody
(using strict locking)
I modified the SelectionTest.tcl script coming with WinCVS 1.1b14 to show
the $fileInfo(locked) files
Unfortunately the following statement seems always to return 1 (file locked)
even
"Locked Files"
proc report_locks {name} {
global cvs
global cvscfg
global cwd
upvar linenum linenum
set linenum 1
set commandline "cvs -l log $name"
catch {eval "exec $commandline"} view_this
set filelist ""
set found "f"
set
)
Regards,
alex.
So here for all of you the WinCVS version (which i enhanced for
multiselected files):
#!CVSGUI1.0 --selection --name "Locked Files"
proc report_locks {name} {
global cvs
global cvscfg
global cwd
upvar linenum linenum
set linenum 1
set
script, which seems to fullfil
my requirements.
Unfortunately the following statement does always return 1 (file locked)
even on unlocked files
... loop over files
cvsbrowser info $file fileInfo
cvsout "-- Locked : " $fileInfo(locked) "\n" -- always 1,
Maybe this is a stupid question, but couldn't find it in the
documentation.
In WinCVS, how do you find all the files that I have locked
(by clicking the lock-key symbol).
Right now, I have to browse each directory manually to see that.
Thomas
28 matches
Mail list logo
