Bug 19865 - [Watch/Edit] Support -l locking
Summary: [Watch/Edit] Support -l locking
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2002-06-10 22:18 EDT by Kevin McGuire CLA
Modified: 2009-08-30 02:25 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin McGuire CLA 2002-06-10 22:18:54 EDT
As posted to eclipse.org, read from bottom up.

====================================================================


Some references FYI.
Kevin

==================================

http://cvsbook.red-bean.com/cvsbook.html#Watches__CVS_As_Telephone_
http://www.loria.fr/~molli/fom-serve/cache/122.html

http://cvsbook.red-bean.com/cvsbook.html#admin (note the line " I'm not sure
how useful this really is,")

-l[REV] - Locks the file's revision to REV. If REV is omitted, it locks the
latest revision on the default branch (usually the trunk). If REV is a
branch, it locks the latest revision on that branch.

The intent of this option is to give you a way to do reserved checkouts,
where only one user can be editing the file at a time. I'm not sure how
useful this really is, but if you want to try it, you should probably do so
in conjunction with the rcslock.pl script in the CVS source distribution's
contrib/ directory. See comments in that file for further information. Among
other things, those comments indicate that the locking must be set to
strict. (See -L.) There is no space between -l and its argument.





"Kevin McGuire" <kevin_mcguire@oti.com> wrote in message
news:a8dben$c2h$1@rogue.oti.com...
> Hi Ali,
>
> CVS doesn't really support this.
> What they do support is called watch/edit, which are both explicit
> additional steps people must take in their workflow and the result is
email
> notification.  See cvs doc (eg. at cvshome.org).  It doesn't have the
> exclusive locking semantics of other repositories but is really just a "by
> participation" notification mechanism.
>
> We are interested in this but likely won't have the cycles to put it in
for
> 2.0.
>
> Kevin
>
>
> "Ali Manji" <amanji@ca.ibm.com> wrote in message
> news:a8d4hq$9bh$1@rogue.oti.com...
> > Hi,
> >
> > For 2.0, will the CVS plugin have a notion of checking out a file
> > "exclusively".  That is, can someone check out a file so that is
> effectively
> > "locked" and no one else can work on it while checked out? If so, what
> would
> > be the context menu item to do this, or if possible could you provide
> > details about how to accomplish this?
> >
> > Thanks,Ali
Comment 1 Michael Valenta CLA 2005-05-09 13:45:58 EDT
There is currently no plan to address this item
Comment 2 Denis Roy CLA 2009-08-30 02:25:36 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.