> Folker, I'm curious to know why you consider TortoiseSVN
> to be unusable in it's current state?
What we don't like with TortoiseSVN is that
it often makes the Exporer unresponsitive some while
(up to several minutes).
Maybe the reason is that our wc has some size now,
and TortoiseSVN has to recusively check the filesystem
or whatever. But such hangs are not cool.
I suppose that this is more a principle problem
of Windows Shell Extensions and not the TortoiseSVN
developer's fault (the windows Explorer is @&$§@,
see this crappy zip-feature of WinXP),
but this does not help in practise.
Maybe there are workarounds for Windows Shell Extensions
(threads etc.), but I am sure that this will cost
a lot of time and work to work-around the Explorer handicaps.
> I have found the TortoiseSVN developers to be friendly
> and responsive to suggestions (e.g. read Stefan's email
> today Re: external diff in .24), so feel free to pass
> on constructive comments to them via the mailing list.
It is more the principle problem mentioned above,
which is not the fault of the TortoiseSVN developers,
so probably I don't have constructive comments.
Personally I will prefer something like WinCVS -> RapidSVN.
This tool is definitely on the right road;
Currently most serious hurdle is that diff is still missing.
It is on their issue-list, therefore it will come some day,
but currently this missing feature makes RapidSVN
basically useless for us.
To emphasis again:
I think that all the Subversion, TortoiseSVN and RapidSVN
teams are doing a very well job!!!!
The problems are partly Windows problems I think,
partly simply a matter of time.
But all in all, as primary-windows-developer,
I am no command-line-tool-fan, but neverthanless
I prefer command-line-svn more than WinCVS.
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 30 03:19:55 2003