Live data from Hacker News

Subversion 1.6 released.

subversion.tigris.org

1–10 of 28 posts

Re: Subversion 1.6 released.

#2
>Subversion 1.6 recognizes a new kind of conflict, known as a "tree conflict". Such conflicts manifest at the level of directory structure, rather than file content.

>Situations now flagged as conflicts include deletions of locally modified files, and incoming edits to locally deleted files. Files and directories which are victims of a tree conflict cannot be committed before the conflict is marked resolved.

Wow - finally! This is great. We've had to handle these edge cases during merges (greatly slowing our scripts) for a long time. Hopefully this will give us significant speed improvements which should help with one of the minor irritants of our users.

Re: Subversion 1.6 released.

#4

>Subversion 1.6 recognizes a new kind of conflict, known as a "tree conflict". Such conflicts manifest at the level of directory structure, rather than file content. >Situations now flagged as conflicts include deletions of locally modified files, and incoming edits to locally deleted files. Files and directories which are victims of a tree conflict cannot be committed before the conflict is marked resolved. Wow - fi…

SVN is basically developing the graph structure that other DVCSs have had ever since their inception (because a DVCS is toast without one and svn can manage).

Re: Subversion 1.6 released.

#6
While many responses are going to be "yawn", especially in the face of the git juggernaut, a great many enterprise systems are locked into svn for the foreseeable future (given economic forecasts, IT departments aren't getting tons of budget for SCM migration / upgrade). Therefore a few extra features coming in are welcome...even if they don't begin with git-

Re: Subversion 1.6 released.

#7
post #6

While many responses are going to be "yawn", especially in the face of the git juggernaut, a great many enterprise systems are locked into svn for the foreseeable future (given economic forecasts, IT departments aren't getting tons of budget for SCM migration / upgrade). Therefore a few extra features coming in are welcome...even if they don't begin with git-

great many enterprise systems - oh please give me a break. Subversion has nothing to do with enterprise blah. Many of us simply use svn because it is a fine tool and gets the job done. For all kinds of projects, from open source to 'enterprise'.

Seriously .. don't put the enterprisey stigma on it. It does not deserve that.

Re: Subversion 1.6 released.

#8
post #7
post #6

While many responses are going to be "yawn", especially in the face of the git juggernaut, a great many enterprise systems are locked into svn for the foreseeable future (given economic forecasts, IT departments aren't getting tons of budget for SCM migration / upgrade). Therefore a few extra features coming in are welcome...even if they don't begin with git-

great many enterprise systems - oh please give me a break. Subversion has nothing to do with enterprise blah. Many of us simply use svn because it is a fine tool and gets the job done. For all kinds of projects, from open source to 'enterprise'. Seriously .. don't put the enterprisey stigma on it. It does not deserve that.

Subversion... the version control system of choice for people that don't understand version control.

Re: Subversion 1.6 released.

#9
post #8
post #7

Earlier quoted context omitted.

great many enterprise systems - oh please give me a break. Subversion has nothing to do with enterprise blah. Many of us simply use svn because it is a fine tool and gets the job done. For all kinds of projects, from open source to 'enterprise'. Seriously .. don't put the enterprisey stigma on it. It does not deserve that.

Subversion... the version control system of choice for people that don't understand version control.

Please feel free to educate us. I use version control and have done for years. I don't branch or merge, and svn works brilliantly for me. It stays completely out the way and allows me to rollback, see changesets, logs, etc if I need. If I wrote a version control system based on my own use case, it'd end up pretty much like svn.

What am I missing?

I've read all the "Git is AWESOME" posts. If I switched to git, it would be exactly the same. It wouldn't solve any problem for my use case that svn doesn't.

Seriously unimpressed with your comment to be honest.

Either make a valid argument as to what I don't understand about version control, or retract it.

Re: Subversion 1.6 released.

#10
Here's a scenario - there are 2 coders working on basically the same base code, but each doing something different. Now the code from both these guys needs to be merged to the base code periodically, so what do you think these guys should use - git or svn , or any other VCS for that matter ?
Post reply on HN