And, I would submit, committing externals from within a different working
copy would be the wrong thing to do.
An external project is a logically and physically separate entity from the
main project. If a developer makes changes in the external project while
working on the main project, those changes need to be vetted differently
than changes in the main project. By the same token, a developer working on
the external project is not working on the main project and needs to deal
with the external project differently.
Donald.
Andy Levy wrote:
> On Mon, Aug 4, 2008 at 06:13, Gabriel <gabrielvdk_at_gmail.com> wrote:
>> Hi,
>>
>> We use the svn-exertnals property quite a lot to include libraries and
>> frameworks into our seperate projects. This all works great. But I
>> think one think you be even easier. The problem is when you commit the
>> root folder of the project everything is commited except for files and
>> folders in the svn-external folders. You need to seperately do this
>> for each external project (in our case: the data project, framework
>> projects & javascript framework).
>
> Externals actually create a SECOND working copy inside the parent WC.
> They have to be committed separately because if the external comes
> from a different repository, it's impossible for the commit to be
> processed as a single transaction.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
--
Donald H Locker
PTM Electronics, Inc
734 426 9010
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-04 13:26:22 CEST