[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Repository know who has checkouts?
Noel L Yap
Re: Repository know who has checkouts?
Wed, 4 Oct 2000 16:35:52 -0400
Short answer: no.
Long answer: If you're using "cvs edit" and "cvs watch", OOTB CVS will keep
track of who has what edited. There's also a patch available (though it may be
dependent on other patches) at SourceForge under project RCVS that'll keep track
of who has what edited where.
BTW, I (and I'm sure many others) would really like the "cvs edit" patches I've
contributed to SourceForge/RCVS to be adopted by CVS (not only for my fame, but
also so I'd get free advertising :-)
Here're the changes again:
1. "cvs edit" fixed to save correct working directory when a path is specified
in the arguments. Absolute paths, rather than relative paths, are used now.
2. Backups allowed over read-only files.
3. Default fileattr set on newly added files.
4. "cvs unedit" changed to chmod a-w files. I don't know if this was already
broken or if I had broken it in one of my other patches.
5. "cvs up -C" fixed so as not to abort when merge is "needed".
6. "cvs up" changed so as to keep the write mode of local files. I don't know
if this was already broken or if I had broken it in one of my other patches.
7. "Too many open files" errors fixed. This bug does exist in cvs-1.10.8, but I
don't think it can be activated. I ran into it when trying to do some of my
1. "cvs edit -c" added to check for editors. If other editors exist on any of
the files to be edited, none of the files to be edited are edited. Otherwise,
all the files to be edited are edited.
2. "cvs edit -f" added to force edit. This is meant to be a command-line
override to those who have "edit -c" in their ~/.cvsrc files.
3. "cvs unedit -e editor" added to allow specification of editor to unedit.
Notifications will be sent to those watching, as always. This allows easier
cleanup of edits after someone has left the group.
4. Multiple edits per user per file allowed. This is useful for those who have
multiple working directories.
5. "cvs ci -c" added to check for valid edits. If the user does not have a
valid edit on any of the files to be checked in, none of the files are checked
in. Otherwise, all files to be checked in are checked in.
1. "rm file; cvs up file" no longer unedits file. "cvs unedit" is meant to
unedit files, not "cvs up".
2. "cvs unedit" changed to keep local modifications. "cvs up -C" is meant to
get a clean copy, not "cvs unedit". This patch also makes "cvs unedit"
non-interactive so that it's batchable.
3. "cvs rel" changed so as not to be interactive.
1. client/server CVS changed so that it logs client username rather than server
username. If you want security, DON'T install this patch. I'm thinking the
right way to do what I want would be to have a mapping from address@hidden to
cvsusername. Of course, this can still be spoofed, but at least any
non-uniqueness in the cvsusernames will be the admin's fault. Of course, I have
zero time to work on this now that I'm not using CVS.
address@hidden on 2000.10.04 15:52:11
cc: (bcc: Noel L Yap)
Subject: Repository know who has checkouts?
Does the CVS repository keep any kind of track of who has checked out? If
it does where does it store this information?
Info-cvs mailing list
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
Re: Repository know who has checkouts?, Derek R. Price, 2000/10/04
Re: Repository know who has checkouts?, Larry Jones, 2000/10/04