John Peacock wrote:
> Mark Phippard wrote:
>
>> 1) With many GUI tools, at least TortoiseSVN and Subclipse, the GUI does
>> not know what files will be committed at the time it would have to
>> request
>> the message template.
>
>
>>
>> 2) TortoiseSVN lets the user start typing their commit message while the
>> code is crawling the WC looking for the changes.
>
>
> Both of these are basically the same thing: the two main GUI's are not
> able to quickly create the actual full commit before the user gets
> bored. This is a limitation of the GUI, since the CLI client has to do
> the same work,
Completely wrong.
Performance is definitely limited by SVN itself, not by TSVN.
Status and commit of a larger tree cost the same time
with TSVN and with command line SVN on windows.
In contrary: The TSVN guys spend a lot of work into working-around this issue,
for example by sacrifying correctness of overlays, or by adding extra
non-trivial logic to their code to optimize data passed to SVN
(causing side effects for the user).
You definitely should take the performance aspect very seriously!
99% of all SVN users work on windows;
and 99% of all windows SVN users use TSVN.
So whatever Stefan and co need - do it!
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 13:11:00 2005