-----BEGIN PGP SIGNED MESSAGE-----
I am new to subversion and new to this list so please forgive me if I ask
something that has gone before (I have checked the archive but can't find an
I am planning a move from an existing complex CVS repository. We have multiple
projects with many elements of shared code. So I am exploring how best to use
the svn:externals properties to pull together each of the projects from the
collection of shared modules.
The first question I have is: what should be the behavior of "svn commit" when
a working copy includes svn:externals specified directories?
My experiments suggest that the commit does not traverse the "external"
directories. Is this the correct behavior? Is there some way to get a "svn
commit" to be applied to the "external" directories.
The problem, as far as I see it, is that developers working on a project that
is made up of a number of shared modules (pulled in to the working copy by
svn:externals) will need to know about all the shared module structure in
order to perform a commit on their working copy. They will need to "cd" into
each separate external directory and do a separate commit. This could lead to
much confusion, for us at least.
An added confusion is that "svn update" does correctly apply to the externals
but "svn status" lists the directories as "?" which is not very consistent.
Am I missing something, or does anyone have any suggestions about how I can
manage this situation?
PS. Thanks to everyone involved in the subversion project for providing such a
fantastic product as open source.
B009 Woodward Building
St. Andrews Road
Worcs WR14 3PS
Key fingerprint = D051 A121 E7C3 485F 3C0E 1593 ED9E D868 A7DA 9FD9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri May 9 09:57:56 2003