<div dir="ltr">On Thu, Jul 31, 2008 at 9:36 PM, Gordon Heydon <span dir="ltr"><<a href="mailto:gordon@heydon.com.au">gordon@heydon.com.au</a>></span> wrote:<br><div class="gmail_quote"><br>Why "head and shoulders above SVN tagging/branching"?<br>
<br>Could you or others making these kinds of assertions possibly justify them?<br><br>They are stated as if they were "self-evident truths".<br><br>I used SCCS for over a decade on various flavors of Unix.<br><br>
CVS was then the new kid on the block, and I used that for a decade and a half.<br><br>Then, SVN, with its very functional tagging and branching system, brilliantly optimized as the economical copying of pointers, have simplified everything and given much better support for binary files, precision directory permissions on the group and user level, a system rich in pre-process and post-process hooks, an API usable by various languages, WebDav (read-only) for basic browsing... <br>
<br>The whole idea of this thread is to discuss how Drupal can be firmly rooted in the tools and workflows that real world developers actually use on an everyday basis, and for good reason; so as to encourage, as webchick wrote, best practices, and, making Drupal convenient, adoptable... <br>
<br>Larry Garfield has explained how for a small core of users, a distributed RCS (such as git, mercurial, etc.) could be superior, but SVN is the most mainstream, is what people actually use.<br><br>git is also creating quite a following among single developers (those not married to a group) who love the "stand alone", local versioning option while retaining the option to "push" (commit) to a server...<br>
<br>You go out and contract repository hosting, as I do, for $7 / month I get unlimited repositories with a TRAC instance for each... cool. Most of these are offering git also.<br><br>With GUI's such as TortoiseSVN and RapidSVN, etc.... it just seems the most attractive and useful way to go.<br>
<br>The only argument against that might make some sense is what Earl Miles said about it probably being a lot of hard work perhaps better spent on other worthy core causes.<br><br>Yet there is something to be said for using tools people use and for good reason.<br>
<br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="Wj3C7c"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Yes this is my major concern with SVN, the total lack of tagging and<br>
branching support.<br>
<br>
Gordon.<br>
</blockquote>
<br>
This just isn't accurate. Several posts in this discussion - not even<br>
all of them being mine - have indirectly or directly explained that svn<br>
does have branching/tagging.<br>
</blockquote>
<br></div></div>
Yes it does have very basic tagging/branching but when you compare this is git, dvcs, etc and even cvs they are head and shoulders above SVN tagging/branching<br><font color="#888888">
<br>
Gordon.<br>
<br>
</font></blockquote></div><br></div>