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

Re: Working Copy Consistency - Switched Folders and Externals Definitions - Embedded or Nested WC - Best Practice

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-07 17:21:20 CEST

You seem to be making a big deal about something I don't understand
the purpose of. What's your use case for this working-area-
encompassing-several-working-copies scenario? I've never seen anyone
work that way. The way our programmers work is that they check out
for example the trunk of a project into a single working copy, and
that's where they work. If the project happens to require other
projects, they're pulled in through externals. Yes, committing in the
main project doesn't also commit changes in the external, but the
external is conceivably used in other projects too, not just this
one, so it's useful that Subversion makes you take a moment to think
whether your changes to the external are appropriate for all projects
that might be using it. It's useful for Subversion to guide the
developer towards the thinking that they should perhaps first enhance
the externally-included library to provide some new feature, and then
in a second (third, fourth, etc.) step modify each project that uses
the external to make use of the new feature.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 7 17:30:47 2006

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.