Subversion 1.10 Released With LZ4 Compression, New Conflict Resolver

[phoronix]

Phoronix: Subversion 1.10 Released With LZ4 Compression, New Conflict Resolver

For those still using Subversion for revision control system for cases like managing of large files or dealing with legacy code-bases, the Apache Subversion 1.10 release is now available...

http://www.phoronix.com/scan.php?page=news_item&px=Subversion-1.10-Released

[F.Ultra]

"those still using Subversion", GIT is not the end all be all solution to revision control. Not everyone works in a highly distributed development environment which is where git apparently shines.

[matthewtrescott]

"those still using Subversion", GIT is not the end all be all solution to revision control. Not everyone works in a highly distributed development environment which is where git apparently shines.

+1. I chose Subversion for my latest project, and would you call LLVM a "legacy codebase"?

[rene]

I much prefer SVN for normal work, GIT is way to complicated / cryptic beyond the usual few commits. Each time I need to do something more I need to google it's esoteric and cryptic command line options first, ..!

[fuzz]

I prefer not to rely on a centralized server to manage commits, even if working alone. That's the end of it. Any other methodology seems absolutely batshit crazy from an architectural point of view.

[Vistaus]

Interesting to see that people are still using SVN. I thought that the people who didn't move to Git moved to Mercurial instead...

[unixfan2001]

I much prefer SVN for normal work, GIT is way to complicated / cryptic beyond the usual few commits. Each time I need to do something more I need to google it's esoteric and cryptic command line options first, ..!

Any example?

[Tuxee]

I much prefer SVN for normal work, GIT is way to complicated / cryptic beyond the usual few commits. Each time I need to do something more I need to google it's esoteric and cryptic command line options first, ..!

Everytime I need to do more than commit and update with SVN I need to google the available commands first... OTOH since I have been working with Git for quite some time now, I don't need to google many "esoteric and cryptic commands".

[King InuYasha]

I much prefer SVN for normal work, GIT is way to complicated / cryptic beyond the usual few commits. Each time I need to do something more I need to google it's esoteric and cryptic command line options first, ..!

This is why I prefer Mercurial. I get the distributed nature that IMO makes version control better, and I don't have insane command syntax.

And, with simple extensions, Mercurial speaks Git and SVN protocols, so it's a better client for both SVN and Git.

[Hi-Angel]

Any example?

"git checkout -- ."

Don't get me wrong, I like git, and ATM at my new work I choose it for a new project even though I know I gotta migrate it to SVN at some point, just because they are using it for all other projects (though I'll try to make them change their mind).

But when I say "I like it", it's because I became good at git. This, however, doesn't change that when I was learning, I never could guess how to do something, and wild guesses on behavior of some random command almost always were wrong. However flexible and great git is, but its command line interface is awful.