Slashdot Mirror
Git 2.8 Officially Released (softpedia.com)
prisoninmate quotes a report from Softpedia: Git 2.8 has been released on March 28, and we have to admit that it comes as a huge surprise to us all. Prominent features of Git 2.8 include parallel fetches of submodules, which allows for the inclusion of other Git repositories in a single Git repo when using the "git submodules" command, support for turning off Git's smudge and clean filters, and support for cloning repos through the rsync protocol. The Git for Windows build received a lot of attention in Git 2.8 and it looks like it's now as comfortable to use as it is on the GNU/Linux and Mac OS X platforms. Also, it is now possible to tell Git not to guess your identity, which, instead, forces you to add a user.name and user.email before doing any commits. Check out the the full release notes for the complete list.
From the second link:
> Support for cloning via the rsync protocol [...] has been dropped.
https://github.com/git/git/com...
you have to download the entire tree, with all releases and branches
If that's an issue for you then subversion might be the way to go. Anything but cvs.
There are very, very good reasons for that. Subversion suffered profoundly from the inability to delete disastrous commits with binaries, mistaken directories, and completely obsolete and deleted projects. This made re-organization of content, even into another repository, very awkward and error prone. Even CVS and professional tools like Perforce were able to completely discard idle directories. The insistence on preserving deleted content also made sanitization of repositories to clear out passwords and password history, or clearing out accidental commits of bulky binaries, very difficult.
If you need a "reference" git repository with all history, certainly create one. But few projects actually need this.
Your comment is funny. I'm pretty sure that you confuse CVS with SVN. :)
There is no reason to be using CVS nowadays when you have an option to migrate to SVN without any headache. Migration to SVN is an easy and straightforward task that brings only benefits and has no downsides.
On the contrary, migration to Git can become a disaster because it is not just about migrating a version-control database to another system, but adopting vague and unclear techniques that don't make your experience using VCS better or anything. Git just makes version-control a different kind of beast you are not used to with SVN or CVS. Migrating to Git involves brain damage, and a can bring more downsides than benefits.
The one real advantage of Git is its distributed nature and fast speed. But this comes with disadvantages such as no locking and no real support for storing binary assets, no access control, unsafe version-history and one of the main disadvantages -- poor support for concurrent work in larger teams.
Still thinking that Git is the one and only version control system that should be used by everyone? Think twice! Git is only one of many VCSes and it has its own disadvantages compared to Subversion or Mercurial. And finally, don't forget that Git is just "a stupid content tracker", a single-purposed tool for hackers designed to be used as a VCS for Linux Kernel. It's not an universal version-control system.