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

Re: Subversion vs VSS

From: Tim Hill <tim_at_realmsys.com>
Date: 2005-04-28 00:54:06 CEST

Jeffrey Allison wrote:

>VSS allows me to share files amongst projects. This is useful to us as we have a number of smallish projects that share some common code. So if three products all need timer.c and I fix a bug in timer.c, all three projects benefit upon the next build. In Subversion the nearest thing to this I can find is externals, but that would imply a blob of common files without the granularity that we have today. Am I missing anything here?
Externals are the nearest, as you say. IMHO the folder-level model
actually helps to encourage best practices -- the file-level sharing in
VSS always gave me the creeps, since it made it too easy for different
projects to become so enmeshed maintenance became horrible.

>Another smaller feature is the ability to refresh a directory of code with the latest from VSS. I simply say "get latest version" from VSS and I get updates to any stale files. I don't have to clear the directory out and grab everything. This isn't a huge deal, but we do this on a pretty regular basis so I think I'd get pushback if this went away.

Er, "svn update" ? Or am I missing something?

>Finally I'm a little underwhelmed by the Tortoise UI that I've been playing with. It's simple and it works, but I think I'd like something a little more powerful. Any suggestions for a Subversion GUI client for Windows?
There is also RapidSVN, but myself I like that Tortoise is integrated
into Explorer.

>- Jeff Allison
> FEI-Zyfer, Inc.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 28 01:44:41 2005

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.