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

RE: FW: RE: Roadmap for 1.1

From: Walter Nicholls <walter.nicholls_at_cornerstone.co.nz>
Date: 2004-04-02 06:06:02 CEST

> we can never totally satisfy a given class of users.

No, but you don't need to *totally* satisfy users to enable them to
switch. If I was totally satisfied with SourceSafe, *nothing* would make
me switch. However, if they rely on something, they can't switch no
matter how much they want to.

In my case, I absolutely rely on locking (shared not exclusive) and
shared files.

For locking there is absolutely no workaround (at sourcecross.org we
have discussed possibilities, but without actually implementing locking
ourselves (or waiting for subversion to do it) we're not going to solve

Shared files are *almost* satisfied by svn:externals: if I had locking
but no equivalent to shared files, then I would move only certain
projects off VSS, use svn:externals judiciously, and retrain users so
they only modify the shared files in their own working copy, pain as it

If I had symlinks for files only, then that would 100% implement what I
am using VSS shared files for and I'd have nothing to keep anything in
VSS any more.

Finally if had symlinks for whole trees, I would be able to implement
what I *wanted* to use VSS shared files for and can't in VSS - and if
those symlinks could point to alternative repositories, I'd be in

I shouldn't have mentioned labels - making a copy (tag) is the correct
way to do it, and if someone really wants to name a revision, they could
use a property. It doesn't help with viewing history quite so well, but
then, because revisions are repository-wide, that history wouldn't
necessarily show the right things.

Speaking of CVS, I did try to switch to CVS many years back, and some of
the reasons I abandoned the attempt have been resolved one way or
another - but the main thing is that I didn't perceive that it was
enough of an improvement to warrant the pain. With Subversion I do -
even though it is in some respects more painful.

I can only speak for myself and in my capacity as a development team
leader, but all these wordy messages really boil down to me urging:

 * Definitely LOCKING
 * Could really really use SYMLINKS
 * If I don't get these, none of the others matter to me in the
 * Tomorrow if possible <g>

- Walter

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 2 05:58:27 2004

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

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