I know this is a late reply, but for what it's worth: I contribute/track about half a dozen large open source projects, all of which use revision control systems (cvs and svn). I have them all checked out into my eclipse workspace. I can't imagine having to do this with tarballs. Some people I know use revisioning not only for source code, but also for flat data files (I dabble in bioinformatics) and article manuscripts (latex). It's genius. Can a tarball tell you who did what, when, and why? The metadata you can get out of svn, from command line - but better yet if integrated in an IDE, is a godsend in collaborative projects. It keeps the managers happy also, what with all the neat graphs you can get out of it using fisheye or ohloh or something. Arguing against it is a losing battle, in my opinion.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
