This is just a short notification that this website has changed home. It was previously hosted free of charge by Free.fr. Although very cheap, this solution had many drawbacks (no MOD_REWRITE for Apache, veeeerrrryyy slow connections, no SSH access, etc.). So I took the plunge and purchased a hosting plan. I went for the basic one from HostMonster and I am currently quite satisfied. The administrative interface is ugly and cluttered but it seems to be the industry standard in those cheap hosting plans (cPanel). I actually chose HostMonster specifically because they were among the few advertising SSH access. With a Terminal and a SSH file system mounted through FUSE, I am a perfectly happy man.
The immediate advantage of the new hosting plan is a more responsive site. And I took advantage of the migration to rework the CSS and give the site a slight face lift. Some AJAX stuff from K2, my WordPress style, are still problematic but I hope to have that resolved soon.
I previously posted a method to move a svn project to git permanently; i.e., without keeping the two-way bridge between svn and git that
git-svn is usually meant to provide. This method involved
git-svnimport. It had the advantage that it somehow transposed the concept of tags from svn to git (in svn tags are really a special kind of branch while tags in git are just labels associated with a commit). But sometimes before git v. 1.6,
git-svnimport disappeared from the git suite. This is a new method using
git-svn which gets all the information out of svn (converting svn tags to git branches) and erases all traces of the original
git-svn bridge. Thanks to the folks on the #git channel at irc.freenode.net for their help in getting this working.
Continue reading ‘Moving from subversion to git permanently – take 2′
I was looking for a convenient way to customize a few community-developed projects and to keep these modifications up to date with the latest stable version of said projects. For example, let say I want to create a custom variation of WordPress version 2.6, (beyond just writing a theme), update it automatically when version 2.6.1 comes out, and be warned if there are conflicts between my customizations and the new code in WordPress 2.6.1. Using two version control systems concurrently (namely git and subversion) eases this situation and prevents losing modifications by accident during the updates.
Continue reading ‘Maintaining personal modifications on top of stable versions of other software projects:
a story of svn, git and git svn’