You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Richard Taylor <r....@eris.qinetiq.com> on 2003/05/09 07:51:44 UTC
Behaviour of svn:externals under commit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
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
answer).
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?
Many thanks
Richard
PS. Thanks to everyone involved in the subversion project for providing such a
fantastic product as open source.
- --
QinetiQ
B009 Woodward Building
St. Andrews Road
Malvern
Worcs WR14 3PS
Jabber: RichardTaylor@jabber.org
PGPKey: http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA7DA9FD9
Key fingerprint = D051 A121 E7C3 485F 3C0E 1593 ED9E D868 A7DA 9FD9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+u14V7Z7YaKfan9kRAm+GAKDjWp7dGee1GLn8zUhQJOAzHXqXdgCg8gag
HcOWY0LPJWO/i/OokNkBGeM=
=CmWD
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Behaviour of svn:externals under commit
Posted by Richard Taylor <r....@eris.qinetiq.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 09 May 2003 9:00 am, cmpilato@collab.net wrote:
> Richard Taylor <r....@eris.qinetiq.com> writes:
> >
> > 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.
>
> This is a known bug. Dunno the issue number off-hand, but I think
> it's scheduled for fixing in one of the next couple of milestones.
>
> > 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.
>
> Another known bug, with a similarly milestone issue.
Thank you for the prompt response. I should have searched the "issues"
database as well as the mailinglist archive :-)
For those who might find this thread in the archive, here are the issue links:
http://subversion.tigris.org/issues/show_bug.cgi?id=1167
http://subversion.tigris.org/issues/show_bug.cgi?id=959
And a further one that picks up on a question that I was going to ask about
taging externals:
http://subversion.tigris.org/issues/show_bug.cgi?id=1258
The first two are targetted for 0.23 and the last one for Post-1.0
Thanks
Richard
- --
QinetiQ
B009 Woodward Building
St. Andrews Road
Malvern
Worcs WR14 3PS
Jabber: RichardTaylor@jabber.org
PGPKey: http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA7DA9FD9
Key fingerprint = D051 A121 E7C3 485F 3C0E 1593 ED9E D868 A7DA 9FD9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+u2O97Z7YaKfan9kRAoxUAJ9hTgyzzpfGZiZqCFX8nyPpEPnT+wCeIyrC
T0zqxPOr0yQmpwuh1g1ppqM=
=LTxu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Behaviour of svn:externals under commit
Posted by cm...@collab.net.
Richard Taylor <r....@eris.qinetiq.com> writes:
> 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.
This is a known bug. Dunno the issue number off-hand, but I think
it's scheduled for fixing in one of the next couple of milestones.
> 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.
Another known bug, with a similarly milestone issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org