Bob Cunningham wrote:
> Still, for the umptyleventh time, let me repeat (FOR THE LAST TIME, I
> promise) that I believe it would be truly useful if the TSVN
> installer would *try* to detect an incompatible CLI as part of the
> install process. The same code may be useful for the Upgrade nag box
> too, to remind the user that their CLI may need to be update along
> with TSVN.
> Better yet would be for the TSVN installer to include its own CLI
> instance, and kill the entire issue (including any possible Cygwin
> issues too!). No need for a version compatibility check, in that
> From my perspective, it's really about being a "one stop, full
> service, Windows SVN client shop". TSVN is the best svn GUI I've
> seen. No, it's more than that: It's the best GUI I've seen for ANY
> revision control product. TSVN is also the best Windows Explorer
> extension I've ever seen (QTTabBar being a distant second).
> If you didn't have such a great product, I wouldn't have nagged so
> hard. TSVN really is that great, verging on "Almost Perfect".
There are too many issues with what you're asking TSVN to do. Thanks
for the input though.
Some questions you may want to answer if you decide to continue this
1. What is *your* definition of incompatible (specifically referring to
SVN clients)? (maybe you'll see the problem when you try to answer this)
2. I have two versions of the command line svn installed on my system
(one is in the default path and is older). How could TSVN detect that
there was another newer svn command line installed?
3. Have you seen the video "How to Protect Your Open Source Project
From Poisonous People"
(granted, the video does devolve into a bit of a whiny
4. Could you also answer Stephan's questions posed in his earlier post?
> PS: Outlook-QuoteFix rocks! Thanks, Andy.
Yes it does. I was also introduced to it from this list.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Aug 6 21:33:07 2007