Hi,
i've been unsind a SCM bridge called 'tailor' between git and svn quite
some time, http://progetti.arstecnica.it/tailor
It integrates with a number of SCM systems and can use both git and
subversion (and CVS) as source and target systems. It works by full
replay, so the changes from the source are essentially repeated on the
target SCM. It could additionally be used to interface with the current
CVS, so we could provide SVN, CVS and git access to the repository
transparently.
Stipe Tolj schrieb:
ok, I'll try to sum up the discussion here:
- user side: git is available at most Linux flavors, but not directly
to other Unix/BSD flavors; git is still more developer affine then
user affine (my perspective on it)
- developer side: git makes life easier in terms that we can commit to
local repos and then "commit remotely" to the master (right?); branch
handling seems to be more effective (Guillaume and Alex claimed this).
My suggestion:
We move to svn on kannel.org, and leave the normal (anonymous)
checkout access to the master repository via svn.
Underneath we can switch to git for those developers who want to.
So a hybrid architecture would be possible IMO. Comments please?!
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------
