[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 1047] New - Pessimistic locking option on checkout made easily configurable
From:       issues () subversion ! tigris ! org
Date:       2002-12-21 13:50:31
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=1047

*** Old
--- New
***************
*** 0 ****
--- 1,33 ----
+ +============================================================================+
+ | Pessimistic locking option on checkout made easily configurable            |
+ +----------------------------------------------------------------------------+
+ |      Issue #: 1047                      Component: subversion              |
+ |       Status: NEW                         Version: current                 |
+ |   Resolution:                            Platform: All                     |
+ |   Issue type: FEATURE                  OS/Version: All                     |
+ |     Priority: P3                     Subcomponent: unknown                 |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: issues@subversion                                            |
+ |  Reported By: prasadgc                                                     |
+ |   QA Contact: issues@subversion                                            |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |    Milestone: TargetMilestone: ---                                         |
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Some developers prefer the policy of pessimistic locking on checkout
+ (which places the onus on the developer checking *out*) rather than an
+ optimistic policy (which places the onus on the developer checking *in*).
+ 
+ It is probably configurable even now, but it isn't in an obvious
+ place. There should be a clear option to set the locking policy
+ (optimistic/pessimistic) at the time a repository is created and even
+ at any point in between.
+ 
+ At the place where I last worked, developers used Microsoft Visual
+ SourceSafe in preference to CVS and Subversion purely for this reason.
+ Please give us an easily configurable locking policy.
+ 
+ Regards,
+ Ganesh C. Prasad
\ No newline at end of file

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
For additional commands, e-mail: issues-help@subversion.tigris.org


[prev in list] [next in list] [prev in thread] [next in thread]