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

Re: A difference in behaviour between CVS/Subversion

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-15 01:03:21 CEST

On May 14, 2005, at 4:58 PM, Nick Glencross wrote:

> Folks,
> forgive me if this has been asked before. I've lurked on and off
> for a while and never seen it discussed.
> One feature of CVS which is nice is that you can checkout a
> directory structure, and then check out other directories into it
> and seamlessly treat it as one project by doing updates and commits
> at the top-level. Each file correctly knows where it lives in the
> CVS depot.
> If you do the same with Subversion, the commit or update doesn't
> descent into the separately checked out directories. As such, you
> need to do (let's say) 4 commits which creates intermediate
> revisions which won't build.
> Was this a deliberate decision?

Yes, though the thought was that someday we'd give the users the
ability to 'link' nested working copies together when they wanted
to. It just hasn't happened yet.

By the way, this behavior you're describing is a relatively recent
addition to CVS, so I've been told.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 15 01:06:08 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.