SwitchToGit

Switch To Git

This page helps us to keep track of steps and decisions which need to be done to migrate to Git.

Descisions/Definitions

• –(Git Username handling… (Standard? proposal: Stefan Agner <stefan@dev.uavp.ch>))–
• Core Migration Path, my Proposal (doesn’t transfer branches):
  1. Delete all branches (All code merged?!) [Will have to be done after convert]
  2. Migrate wolferl-ng/trunk to one Git repository
  3. –(Delete)–Make read-only wolferl-ng on Subversion (head)
• How to access git repositories? –(Proposal: git@dev.uavp.ch, send ssh public key by E-Mail to amir, ready to go!)– Already setup exactly like this

Tasks

1. Trac update (auf 1.0)
2. Close SVN remote write access [Yes, sure]
3. –(Delete)– Make read-only all wolferl-ng/branches
4. Migrate wolferl-ng/trunk to Git repository (check tags too, keep users.txt in mind, use [1] and see http://git-scm.com/book/en/Git-and-Other-Systems-Migrating-to-Git) -> git2svn-sync.sh –servere is able to do that.
5. –(Delete)– Make read-only wolferl-ng/trunk
6. Migrate Commit-Mailinglist to git (git hooks)
7. Ilogbot extention for git
8. Git Support for: release.sh/gen.daily.sh
9. Git Support for Build: configure.ac

[1] svn log https://dev.uavp.ch/pw/wolferl-ng/ –xml | grep -P “^<author” | sort -u | perl -pe ’s/<author>(.*?)</author>/$1 = /'