Op 12-3-2012 18:15, Rob Oakes schreef:
On Mar 12, 2012, at 10:59 AM, Abdelrazak Younes wrote:
The main repo would be automatically synchronized (only the 2.0 and
2.1 branches); either via a git hook or a cron script at server side.
The cron idea is better if only we had some automatic regression
testing in place. Then only those commits that passes regression on
the cooking repo would be pushed to the main repo.
Would it be possible to have the main repo also synchronized with the existing
SVN? git-svn can transparently push right to an SVN repository.
Not anymore, the HEAD of the git repo has a different sha1 as the svn
repo imported by git-svn. This because some tags and strange commits
have been corrected in the git repo.
That would prevent a lot of things from breaking. For example, I've been
keeping a mirror of SVN on Launchpad that I use for development, testing, and
(hopefully) daily builds. Retooling this mirror to pull from git would require
re-importing the whole thing (a multi-day affair).
Would it be really a multi-day affair ? Cloning the git repo is done
within a minute, and you have the whole history with it.
Vincent
