On 2015-06-03 18:17:26, Andrew Fish wrote: > On Jun 3, 2015, at 5:59 PM, Roy Franz <roy.fr...@linaro.org> wrote: > Honestly if the choice comes down to an EDK2 upstream being git with > 40 submodules, or > a single SVN repository (with a git mirror), I'd rather have the > single SVN repository. > I'd never use SVN, but just use the git mirror. The maintainers would > would > still need to use SVN, but that's not my problem :):) The people that > want to use SVN > could use SVN, and those that want to use git (except for > maintainers/committers :) could > use git. > > You can commit to svn from git. > git svn rebase > git svn dcommit > git svn info
git svn makes svn based development sane, but it is inferior. It doesn't really support all git features. It also has a natsy gotcha where equivalent branch get artificially split. For example, my 'git-svn' at top-of-tree is never considered the same as origin/master. This prevents things like 'git merge' from being usable. Of course, 'git merge' can't be used with git svn anyhow... It also causes the source control history to be needlessly duplicated for the two branches. An example of how this wastes time is that I do my development based on the git origin/master branch. But, when it comes time to commit to svn, I checkout the git-svn branch, run git svn rebase, cherry-pick all the changes to the git-svn branch, and finally use git svn dcommit. Contrast this to just running 'git push'. -Jordan ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
