Note to self: svn:ignore usage # Putting the information here to make retrieving it a bit easier next time. When working with svn and some random IDE I’d really love to avoid checking in any files that are IDE specific (project configuration, classpath, etc.). The command to do that: svn propedit svn:ignore $directory_to_edit After issuing this command you’ll be prompted to enter file patterns for files to ignore or the directory names. ...
First steps with git # A few weeks ago I started to use git not only for tracking changes in my own private repository but also for Mahout development and for reviewing patches. My setup probably is a bit unusual, so I thought, I’d first describe that before diving deeper into the specifc steps. Workflow to implement With my development I wanted to follow Mahout trunk very closely, integrating and merging any changes as soon as I continue to work on the code. ...
Converting a git repo to svn # Pretty unlikely though it may seem, but there are cases when one might want to convert a git repo to svn and still keep all revisions intact. There is a nice explanation online on how to do that in the Google Open Source blog.
Keeping changesets small # One trick of successful and efficient software development is tracking changes in the sources in source code management systems, be it centralized systems like svn or perforce or decentralized systems like git or mercurial. I started working with svn while working on my Diploma thesis project in 2003, continued to use this systems while researcher at HU Berlin. Today I am using svn at work as well as for Apache projects and have come to like git for personal sandboxes. ...