Molle Bestefich wrote:
> Simon Large wrote:
>>>> If you commit a WC containing externals, TSVN tells you that
>>>> they have to be committed separately. Conversely, updates always
>>>> update the externals too.
>>>
>>> Hopefully they will just be committed without having the user browse
>>> to each and every darn folder and clicking commit. At least that's
>>> what my TSVN does, which we happen to rely on a lot :-)
>>
>> Huh? That's not what happens for me in 1.2.0 RC2. If I try to commit
>> the parent folder I get a dialog saying:
>> There are changes inside one or more directories which you have
>> included with svn:externals.
>> Those files are <b>not</b> listed for commit. You need to commit
>> those files separately.
>
> Just installed RC2, and for me it commits the external stuff correctly
> without a hitch?
> Yes, I remembered to reboot ;-).
>
> We're using svn:externals for references to shared files which are
> internal to the repository, so perhaps TSVN recognizes that the files
> are internal and commits them? That would be beautiful.
Aha! That's the difference. Externals in the same repository are
committed automatically. Externals in a different repo are not. Off I go
to update the docs again ...
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu May 26 17:34:53 2005