Thank you everyone for your experiments and responses.
I wish the behavior of externals was configurable.
I'm glad commit doesn't recurse.
For now, I've told my colleague to use the command line version of Subversion
and to always add the -N flag (don't recurse).
Unfortunately, that doesn't appear to be an option with Tortoise.
Eventually (the beginning of next year perhaps), we'll try to use externals.
At least we'll know that commit doesn't recurse.
Thanks,
Chuck
-----Original Message-----
From: Jan Evert van Grootheest [mailto:j.grootheest@euronext.nl]
Sent: Friday, December 12, 2003 4:17 AM
To: 'cdoucette@med-learn.com'; users@subversion.tigris.org
Subject: RE: use of svn:externals (does Subversion recurse into external directories?)
Chuck,
we're doing something comparable here.
The checkout, update and status commands automatically recurse into the externals. However, comit does not.
We've had no problems with it other than users that need to get explained how and why.
-- Jan Evert
-----Original Message-----
From: Charles E. Doucette [SMTP:cdoucette@med-learn.com]
Sent: Thursday, December 11, 2003 3:08 PM
To: users@subversion.tigris.org
Subject: FW: use of svn:externals (does Subversion recurse into external directories?)
Does anyone have any feedback for my question?
I suppose I can try an experiment but I'd rather just get some expert
advice and reorganize our actual project.
Thanks,
Chuck
-----Original Message-----
From: Charles E. Doucette [mailto:cdoucette@med-learn.com]
Sent: Tuesday, December 09, 2003 7:37 PM
To: users@subversion.tigris.org
Cc: 'Stas Taraschansky'
Subject: use of svn:externals (does Subversion recurse into external directories?)
We are developing a few (ASP.NET) website projects using Subversion.
One of the websites has subdirectories with thousands of loosely-coupled multi-media files (which takes hundreds of
megabytes).
This files do change occasionally, and they should be in synch. with the code, so, we'd like to track them with version
control;
however, it is quite rare.
I thought perhaps all of the subdirectories with multi-media files could be constructed via svn:externals (a property I
would have
to set on the top-level directory).
My question is would Subversion automatically traverse into the subdirectories with the multimedia files, or would it only
apply to
the files and subdirectories which were part of the original tree in the repository (without the externals)?
If so, perhaps we can reorganize things with externals so that normal commands (status, update, commit etc.) would work
*much*
faster? Then, if/when we needed to perform operations on the directories with multimedia files we could cd to those
directories and
perform those operations explicitly?
Thanks,
Chuck
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
=== E U R O N E X T - D I S C L A I M E R =============================
This e-mail and its attachments are only intended for the individual(s) or entity(entities) named above to whom they are addressed
and may contain personal and/or confidential information. Please notify us immediately if you are not the intended recipient. Any
dissemination, duplication, publication to third parties or other use of the contents of this e-mail or its attachments is
forbidden. Although this information has been compiled with great care, neither Euronext N.V. nor its subsidiaries shall accept any
responsibility for any errors, omissions or other inaccuracies in this information or for the consequences thereof, nor shall it be
bound in any way by the contents of this e-mail or its attachments. In the event of incomplete or incorrect transmission please
return the e-mail to the sender.
Cet e-mail et ses annexes sont uniquement destinés à la (aux) personne(s), ou à l' (aux) entité(s) à laquelle (auxquelle(s)) il est
adressé, visée (s) en tête du présent message. Il peut contenir des informations personnelles ou confidentielles. Merci de nous
notifier immédiatement si cet e-mail vous a été adressé par erreur. Toute diffusion, copie, publication à des tiers ou toute autre
utilisation de son contenu est interdite. Bien que cette information ait été rassemblée avec une grande attention, ni Euronext N.V.
ni aucune de ses filiales, ne peut être tenue responsable des erreurs, omissions ou inexactitudes contenues dans cette information,
ni ne peut être liée d'aucune manière par le contenu de cet e-mail ou ses annexes. En cas de transmission incorrecte ou incomplète,
nous vous prions de retourner cet e-mail à son émetteur.
Deze e-mail en zijn bijlagen zijn uitsluitend bestemd voor de geadresseerde(n) als op dit e-mailblad vermeld. Het is mogelijk dat
deze e-mail persoonlijke en/of vertrouwelijke informatie bevat. Wanneer u niet de geadresseerde bent, verzoeken wij u dringend ons
daarvan te berichten. Elke verspreiding, vermenigvuldiging, gebruik of openbaarmaking aan derden van de inhoud van deze e-mail en
zijn bijlagen, is verboden. Hoewel deze informatie met de meeste zorg is samengesteld is Euronext N.V., en de tot Euronext N.V.
behorende werkmaatschappijen, op geen enkele wijze aansprakelijk voor eventuele fouten, omissies of andere onjuistheden in deze
informatie of de gevolgen daarvan noch op enigerlei wijze gebonden aan de inhoud van de e-mail of zijn bijlagen. Gelieve, in geval
van onjuiste of onvolledige ontvangst, deze e-mail terug te sturen naar de afzender.
================================
Received on Fri Dec 12 22:22:21 2003