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