[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]



On Thu, 2004-01-15 at 18:15, Danny Cox wrote:
> John,
> 
> On Wed, 2004-01-14 at 08:56, John Wells wrote:
> > I'm in a position to decide on a versioning control system for our
> > company's dev team.  Naturally, my first thought was CVS, but I've seen a
> > few blips for Subversion (subversion.tigris.org) and must say I like some
&gt; &gt; of the features (<a  rel="nofollow" href="http://svnbook.red-bean.com/html-chunk/ch01s03.html";>http://svnbook.red-bean.com/html-chunk/ch01s03.html</a>).
&gt; 
&gt; &gt; Anyone out there using Subversion?  What's your experience regarding
&gt; &gt; stability and usefulness?  Any caveats or kudos?
&gt; 
&gt; 	I've not used it, but it's been self-hosting for over a year now. 
&gt; That's got to be a testimony, but see below.
&gt; 
&gt; 	Caveat: any sufficiently advanced technology is indistinguishable from
&gt; a rigged demo ;-)
&gt; 
&gt; 	As I recall the story, Linus wanted a specific feature that didn't
&gt; exist in ANY version control system at the time, and I don't know if
&gt; I'll be able to explain it properly or not, but here goes:
&gt; 
&gt; 	given a kernel driver/feature/project,
&gt; 	fork it: one branch shows up in the &quot;standard&quot; kernel
&gt; 	the other one is developed
&gt; 	continue accepting patches for both branches
&gt; 	when the &quot;new&quot; branch is &quot;ready&quot;, logically swap the
&gt; 	branches, then drop the &quot;old&quot; one.
&gt; 
&gt; or something like that.  The developer of BitKeeper, what's-his-name was
&gt; visiting Linus and the began a discussion that resulted in the
&gt; development of BitKeeper, BitMover (the company), and ultimatly, fights
&gt; between what's-his-name and most of the linux kernel community :-(.
&gt; 
&gt; 	The main problem(s) with CVS is that it doesn't understand file
&gt; meta-information.  For example, you can't rename a file.  Well, you can,
&gt; but you must know what you're doing.  Renaming a directory is even
&gt; harder.  But, it'll handle file changes like a champ.
&gt; 
&gt; 	Have I rambled enough?  Sorry.
&gt; 
&gt; 	Caveat Emptor!
&gt; 
&gt; 	Up the Universe!


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00610" href="msg00610.html">[ale] Subversion?</a></strong>
<ul><li><em>From:</em> fletch at phydeaux.org (Fletch)</li></ul></li>
<li><strong><a name="00611" href="msg00611.html">[ale] Subversion?</a></strong>
<ul><li><em>From:</em> jasonday at worldnet.att.net (Jason Day)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00526" href="msg00526.html">[ale] Subversion?</a></strong>
<ul><li><em>From:</em> jb at devsea.com (John Wells)</li></ul></li>
<li><strong><a name="00603" href="msg00603.html">[ale] Subversion?</a></strong>
<ul><li><em>From:</em> danscox at mindspring.com (Danny Cox)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00604.html">[ale] instruction needed</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00606.html">[ale] instruction needed</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00603.html">[ale] Subversion?</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00610.html">[ale] Subversion?</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00605"><strong>Date</strong></a></li>
<li><a href="threads.html#00605"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>