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.
Archive for the 'post' Category
Page 2 of 7
A very delicate matter when publishing photos on the web (or anywhere actually) is color management. What looks good on one monitor usually looks different (read: “bad”) on another one, or on paper. My goal is to publish pictures taken with a Canon EOS 40D camera in web galleries (ZenPhoto, Gallery, Flickr, etc.) or flash based galleries (such as SimpleViewer). I use Apple Aperture to manage and edit my pictures on a MacBook. Here is what I have learned and decided to use.
Continue reading ‘Getting colors right from the camera to the web,
through Apple Aperture’
New versions of git make the information on this page obsolete.
Please see my new post about this.
There are plenty of tutorials and blog posts out there regarding how to move from subversion to git smoothly. In those, the goal is often to keep svn as the public frontend but to spend most of the day in git, only interacting with svn through git-svn. My goal here is a bit different: I want to permanently move all my code to git and get rid of the svn repositories after the migration is complete. In the process, I want to cut my svn repositories in small pieces and make each of those a separate git repository. This involves git-svnimport and the steps are described below.
Continue reading ‘Moving from subversion to git permanently’
Recent Comments
a Subversion application