RE: Feature Request: svn:externals dialog update...

>> If you really want to keep 100% consistency between the server
>> capabilities and the client user interface, the simplest solution is
>> to use clients and servers from the same generation...
> SVN itself supports interactions with multiple combinations of
> clients and servers. TSVN should not break that capability.

I think you may have misread what I wrote. I'm not talking about compatibility, I'm talking about user interface consistency.
IMHO TSVN keeps compatibility; by offering the "Advanced" edit field.

...

> TSVN should do the same without forcing people to have to remember
> how to do it all the time as it only takes one slip-up to break
> the system in that case.

If it is that easy to break your system, I would strongly suggest that you implement a server side hook that prevents those kinds of commits. In the error message you can inform the users of how to avoid the error.

Even if TSVN would implement an option to do what you want per default, it would only take one user that forgets to set the option to cause problems for you. Start with the hook.

>> PS. Of course, another way would be to modify TSVN yourself to do
>> seamless fallback for your use case; use that version yourself and
>> offer the patch to the list. DS.
> Well, from what I understand TSVN has a specialized environment
> which I don't have the capabilities to build on Windows; nor do I
> have the time to setup at the moment. I have considered it.

It's not very specialized. It does requires a very recent version of Visual Studio though... :-/

Hans-Emil

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2876544

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-09 10:13:23 CET