On Thu, 16 May 2019, Maxim Kuvyrkov wrote: > Let's avoid mixing the two discussions: (1) converting svn repo to git > (and getting community consensus to switch to git) and (2) deciding on > which branches to keep in the new repo. > > With git, we can always split away unneeded history by removing > unnecessary branches and tags and re-packing the repo. We can equally > easily bring that history back if we change our minds.
A prerequisite of a move to git is to have policies on branch deletion / force-pushes, and hook implementations that ensure those policies are followed (as well as implementing what's agreed on commit messages, Bugzilla updates, etc.). There has of course been a lot of past discussion of those that someone will need to find, read and describe the issues and conclusions from. I think there was a view that branch deletion and force-pushes should be limited to a particular namespace for user branches. (I support a move to git, but not one using git-svn, and only one that properly takes into account the large amount of work previously done on author maps, understanding the repository peculiarities and how to correctly identify exactly which directories are branches or tags, fixing cases where there are both a branch and tag of the same name, identifying which tags to remove and which to keep, etc.) -- Joseph S. Myers jos...@codesourcery.com
