[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Subversion post 1.0 features (was Subversion history: Why was/is tagging/branching implemented as copy?)

From: Carsten Schurig <carsten.schurig_at_ebz-dresden.de>
Date: 2003-11-04 09:26:56 CET

Walter Nicholls <mailto:walter.nicholls@cornerstone.co.nz> wrote on
Monday, November 03, 2003 11:22 PM:

> I think "Locking" (also called "Reserved Checkout") should be stated
> on the main Subversion home page (http://subversion.tigris.org/) as a
> post-1.0 feature. It is on the issue list
> (http://subversion.tigris.org/issues/show_bug.cgi?id=533) but this is
> almost a first asked question for many users and is a critical feature
> supported by practically every other VC system (yes, even CVS).
> For me it's a killer. It's not a Subversion technology issue, it's a
> client technology issue. There are tools out there with source control
> models that do not fit Subversion's model and to use Subversion as a
> back-end absolutely require locking.

+1 from me.

We are developing mainly in LabVIEW and that stores files binary. You
can do a compare using LabVIEW (metadiff+lvdiff) but you can't do a
merge, though. It would be nice to let the other developers know that
one's working on a specific file (tree). (But as we're just three people
it's not such a big problem yet.)

But nevertheless SVN is far more sophisitcated than the integrated
source code control system of National Instruments wich does locking
(and forgets sometimes to unlock properly).

Keep up the good work,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 4 14:48:43 2003

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.