On Dec 14, 2010, at 11:43 PM, Damien Pollet wrote: > On Tue, Dec 14, 2010 at 23:13, laurent laffont > <[email protected]> wrote: >> Not my priority at the moment :), but you can have a look at git svn >> command ( http://progit.org/book/ch8-1.html ) so you can work with both git >> and svn and keep history. > > The other Damien used that for the "by example" books. It works well > to import the whole history, and I think for tracking authorship it > would be a good idea. > > However, it would probably become an organization nightmare if people > commit to both svn and git.
yes please don't :) Let people knowing and forcing to do that do it. > Someone has to keep a git-svn clone somewhere and periodically update > from svn and push/merge to git. Of course, unless there is a branch > under git just for that, as soon as there is a merge conflict, human > intervention will be needed. Also, that git-svn clone must not be > lost. I'm not sure you can re-build it and the checksums will still > match those on the git side. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >
