How we plan to cleanup the repository:

Task	Should we do it?	How to implement?	Already implemented by?
remove useless tags/optik-1.5 branch	yes	reposurgeon 'delete obliterate'	done, hartmut
Remove changes to tag-branches after tagging (e.g. svn:eol-style)	yes	reposurgeon 'delete xxx obliterate'	done, hartmut
Remove renaming of tags to original tagging commit	yes	reposurgeon 'delete xxx '	done, hartmut
Cleanup tagging errors around several releases	yes	re-tagging (04-retag.sh)	done, hartmut
Cleanup wrong copy trunk to tags/RELEASE_1_0/trunk (1.0-rc1)	yes	re-tagging (04-retag.sh)	done, hartmut
merge some commits which revert or fix the one before (or such)	yes	reposurgeon	done, hartmut
remove some other garbage	yes	reposurgeon	still looking for garbage
Cleanup "r324@rosen" commit messages	yes	git filter-branch --msg-filter helper-git-filter-clean-msgs.py	done, hartmut
Cleanup long merge commit messages , e.g r543	yes	git filter-branch --msg-filter helper-git-filter-clean-msgs.py	done, hartmut
Add parents when feature-branches were merged to trunk	yes	git filter-branch --commit-filter
Add parents based on meta-data from SVN-merge	?? be be decided	maybe	added some, hartmut
rewrite merge messages to have a better "subject"	no	git filter-branch --msg-filter git-svn-abandon/git-svn-abandon-msg-filter	done when recreating svnmerge messages
remove non-tag and non-head binaries (.exe, .dll, etc.)	no		would save space, but seams to be complicated
task	yes/no	how	impl
rewrite log messages to match convention	yes	manually, reposurgeon	done, hartmut
prefix tag names with 'v'	yes	done when re-tagging (04-retag.sh)	done, hartmut
rename master (ex. trunk) to develop rename tags to master	if following ​http://nvie.com/posts/a-successful-git-branching-model	git branch -m master develop more tips at git-svn-abandon/git-svn-abandon-fix-refs or look at reposurgeon	done, hartmut
finall cleanup and compression	yes	reposurgeon gitsvnparse and see man-page of git-filter-branch and scripts in git-svn-abandon/	done, hartmut