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

Re: Idea regarding working copy, .svn location, and some more

From: <cmpilato_at_collab.net>
Date: 2003-07-31 16:36:10 CEST

pmarek@users.sourceforge.net writes:

> > But wait a second. Now my users are blissfully unaware that they are
> > looking at versioned data, so they go moving things around willy nilly
> > using the regular filesystem commands -- without using Subversion, and
> > without "changing the paths in [the] config area". Now my working
> > copy is completely out of whack! Where's the goodness in that?
> That's the same as now. Now they move directories around, and svn doesn't
> automatically move the files in the repository.
> But wait, there's a perl-script for doing imports, isn't it? :-)

Erm... you've missed the point. Today, users move directories around,
and those directories are still valid working copies that point to
valid repository locations. Sure, they don't necessarily maintain the
same heirarchy as what is in the repository, but they still work (sans
implementation bugs), and since we're not hiding the fact that they
are Subversion working copies, the users have a visual reminder that
just using filesystem move operations might not be the best way to
rearrange their data.

You can't tout user ignorance as a feature when that ignorance is both
unnecessary and burdensome.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 31 16:38:35 2003

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.