You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Pavel Radzivilovsky <pa...@tase.co.il> on 2005/04/05 11:25:06 UTC

SVN improvements

Dear SVN Guys,

Perhaps you would be interested to see this. I'm forwarding you a part of my conversation about changing the source control system in the (big) organization I'm working for (http://www.tase.co.il). This is an explanation why a suggestion to drop Microsoft VSS in favour of Subversion was turned down after a research.

Hopefully you will find it useful to improve certain things to match existing industry's requirements, because personally I would prefer to use Subversion to anything else :)

Best Regards,
Pavel

-----Original Message-----
From: vadim 
Sent: Tuesday, April 05, 2005 11:02 AM
To: Pavel Radzivilovsky
Subject: [Fwd: FW:]


mayhaps it should be forwarded to SVN developers.

-------- Original Message --------
Subject: 	FW:
Date: 	Tue, 5 Apr 2005 11:13:50 +0200
From: 	Pavel Radzivilovsky <pa...@tase.co.il>
To: 	<va...@melig.co.il>





  -----Original Message-----

*From:  * Shai Berger

*Sent:  * Tuesday, April 05, 2005 10:22 AM

*To:    * Pavel Radzivilovsky

*Subject:       * RE:

We thought that trying to teach people about copy-edit-merge while
taking away the Visual Studio integration would not fly. While
TortoiseSVN (the Windows Exploerer plug-in) is a fine product, AnkhSVN
(the VS.NET plug-in) was not ready for general use at the time we tried
it (version 0.5.5). Version 0.6 is still not out, and I don't know how
much it will fix.

I think when we talked yesterday, I said what I think: As a pure
source-control program, Subversion is better than SourceSafe, period. An
order of magnitude better. If we were starting from scratch, I would
prefer the not-integrated TortoiseSVN to the integrated SourceSafe.
However, we are not starting from scratch. If we change something, it
needs to be perceived as an improvement. The way things stand now, we
would just be replacing one set of problems for another; the SVN set of
problems would affect more people more of the time, and they would be
less sophisticated users than the ones who run into SourceSafe limitations.

        -----Original Message-----

       *From:  * Pavel Radzivilovsky

       *Sent:  * Tuesday, April 05, 2005 10:08 AM

       *To:    * Shai Berger

       *Subject:       * RE:

       So  where is it stuck?

              -----Original Message-----

             *From:  * Shai Berger

             *Sent:  * Tuesday, April 05, 2005 10:02 AM

             *To:    * Pavel Radzivilovsky

             *Subject:       * RE:

             Thanks. You know, though, that I don't need to be convinced.

                    -----Original Message-----

                   *From:  * Pavel Radzivilovsky

                   *Sent:  * Tuesday, April 05, 2005 7:59 AM

                   *To:    * Shai Berger

                   *Subject:       *

                   http://subversion.tigris.org/testimonials.html

                   Pavel, 673

                   054-4818021

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org


Re: SVN improvements

Posted by "Brian W. Fitzpatrick" <fi...@collab.net>.
On Apr 5, 2005, at 6:42 AM, John Peacock wrote:

> Pavel Radzivilovsky wrote:
>> We thought that trying to teach people about copy-edit-merge while
>> taking away the Visual Studio integration would not fly. While
>> TortoiseSVN (the Windows Exploerer plug-in) is a fine product, AnkhSVN
>> (the VS.NET plug-in) was not ready for general use at the time we 
>> tried
>> it (version 0.5.5). Version 0.6 is still not out, and I don't know how
>> much it will fix.
>
> You may want to do a little more research.  There is a commercial SCC 
> plugin for Subversion available from PushOK:
>
> 	http://www.pushok.com/soft_svn.php
>
> which integrates very well into whatever SCC IDE you choose to utilize 
> (including VS.NET).  It does not use the bindings, but rather drives 
> the commandline utility via a GUI.  I actually suggested that the 
> developers create the Subversion plugin, since I was very happy with 
> the CVS plugin that they also created.

In addition, Subversion 1.2 should be released shortly, and it supports 
file locking (also known as "reserve checkouts").

Good luck,

-Fitz


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: SVN improvements

Posted by John Peacock <jp...@rowman.com>.
Pavel Radzivilovsky wrote:
> We thought that trying to teach people about copy-edit-merge while
> taking away the Visual Studio integration would not fly. While
> TortoiseSVN (the Windows Exploerer plug-in) is a fine product, AnkhSVN
> (the VS.NET plug-in) was not ready for general use at the time we tried
> it (version 0.5.5). Version 0.6 is still not out, and I don't know how
> much it will fix.

You may want to do a little more research.  There is a commercial SCC plugin for 
Subversion available from PushOK:

	http://www.pushok.com/soft_svn.php

which integrates very well into whatever SCC IDE you choose to utilize 
(including VS.NET).  It does not use the bindings, but rather drives the 
commandline utility via a GUI.  I actually suggested that the developers create 
the Subversion plugin, since I was very happy with the CVS plugin that they also 
created.

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org