Switching from SVN to Git

By britt

posted in: announcements, documentation, programming

We are switching our version control repository from Subversion to Git. Initially I read Why Distributed Version Control Matter to You, Today and shrugged my shoulders and said, “Maybe so, but subversion works fine.” However we recently ran into a situation where we needed more robust branching and merging features than Subversion had to offer, combine that with GitHub’s easy setup and awesome interface, and we were sold.

From now on HiveDB and HiveDB-Blobject will be located at:

  • HiveDB (git://github.com/britt/hivedb.git)
  • Blobject (git://github.com/britt/hivedb-blobject.git)

The old subversion repository will stay online but no new code will be added to it.

To get the source code you can run

git clone git://github.com/britt/hivedb.git

or you can download the tarball.

Download source tarball from GitHub

More info on git

P.S. This maybe the first time that we have mentioned the hivedb-blobject project on the blog. There is more information to come, but the short description is that Blobject is a library that plugs into Hibernate and lets you store the bulk of an object as a serialized blob. Why would you want to do this you might ask? Well, an alter statement on 10^9 rows doesn’t complete very quickly. Blobject lets you store the bulk of your objects as serialized blobs. This way you can store multiple versions of the blob schema in the database simultaneously and upgrade them on demand as they are retrieved.

One Comment

  1. Alex Li added these pithy words on May 30, 2008 | Permalink

    It is a wonderful move to stay away from SVN.

    Unfortunately, Git seems does not handle file rename/move well either during merge time. This is terrible if you do refactoring a lot in Java. That is the main reason we are switching to bazaar instead. More to read here: http://www.markshuttleworth.com/archives/123

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*