tag:blogger.com,1999:blog-1383695822029623916.post2324350831934108577..comments2024-03-28T00:20:38.908-04:00Comments on Chris Wong's Development Blog: DVCS for all the wrong reasonsChristopher Wonghttp://www.blogger.com/profile/16941177380839071164noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-1383695822029623916.post-86894584255980211032011-02-15T05:53:17.936-05:002011-02-15T05:53:17.936-05:00DATE: 2011-02-15
SVN 1.7.0 is feature complete.
N...DATE: 2011-02-15<br />SVN 1.7.0 is feature complete.<br /><br />Now lets have a look at your list and what was done<br /><br />* WC-NG: New metadata library. While it fixes the .svn directory littering in the workspace, there is no mentioning about better merging<br /><br />What else? I don't see anything else...Unknownhttps://www.blogger.com/profile/16515777241926381830noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-73155937832778419642010-11-12T19:57:48.428-05:002010-11-12T19:57:48.428-05:00Regarding the "Distributed" versus "...Regarding the "Distributed" versus "Centralized" argument, I think you're missing the point that Linus' repo is the center of linux kernel development. He may be pulling from various downstream lieutenants, but he's effectively acting as the server hosting the master repository. Anyone who wants to pull pulls from Linus. They check in lower downstream, and code banzaimonkeyhttps://www.blogger.com/profile/10460566955480079922noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-54200693082669472162010-11-04T01:52:11.000-04:002010-11-04T01:52:11.000-04:00We switched our project from ClearCase (I know, I ...We switched our project from ClearCase (I know, I know) to Git about a year ago, and we're never going back.<br /><br />Your article makes some good points in regards to "going dark" and such, but in practice I don't think this will be a problem in any reasonably managed project. People would notice that this person "never" pushes his or her changes out. <br /><br />Infredrikhttps://www.blogger.com/profile/08833756769211183446noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-92094675490270744772010-11-02T15:47:10.107-04:002010-11-02T15:47:10.107-04:00In my opinion, SVN is over. You left out the issue...In my opinion, SVN is over. You left out the issues od speed, file handling, the tedious ignores system, the .svn folder litter, the issues with file copy/move, only to name a few. <br />While I would not advocate git, since its usability is best described as hostile, there are good alternatives such as recent Mercurial.<br />And the central repository as enforced by versioning system argument Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-50738885520479174072010-10-31T08:52:53.824-04:002010-10-31T08:52:53.824-04:00Let's assume that Subversion somehow gets equi...Let's assume that Subversion somehow gets equivalent of "git bisect" / "hg bisect" (it can be hard with model of branching used in Subversion), which can be used to find commit that introduced a bug (something that is probably called "diff debugging" in Subversion), or that Subversion users do find such commit using "svn annotate" / "svn blame"Jakub Narebskihttps://www.blogger.com/profile/11847202568800326989noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-82634702756580592892010-10-31T07:02:16.647-04:002010-10-31T07:02:16.647-04:00I don't think that it would be easy, if at all...I don't think that it would be easy, if at all possible, for Subversion to get support for merging on the par of the one used by Git, especially in more complicated situations (file renames, criss-cross merges, etc.). The difficulty of handling merging in Subversion is caused by the model of branches that Subversion uses (branches are copies, branch history is just history path-limited to Jakub Narebskihttps://www.blogger.com/profile/11847202568800326989noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-17051857372575789822010-10-29T16:28:29.650-04:002010-10-29T16:28:29.650-04:00Ahem. http://bit.ly/cMHm9vAhem. http://bit.ly/cMHm9vPete Brattonhttps://www.blogger.com/profile/17870155103656342280noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-67292751815414846982010-10-29T15:30:15.844-04:002010-10-29T15:30:15.844-04:00Hey Chris,
I'd argue that:
a) distributed sys...Hey Chris,<br /><br />I'd argue that:<br />a) distributed systems don't have to be hierarchical,<br />b) "offline commits" really just simulate the distributed repositories<br /><br />A hub-and-spoke network with repositories at the end of the spokes is definitely distributed. It's just not a full mesh network.<br /><br />That said, I do think that git's complexity is aunscriptablehttps://www.blogger.com/profile/07274735438320909148noreply@blogger.com