[Axiom-developer] SCMs

[C Y]

A question, to the list in general and more specifically to those
maintaining branches.

If someone were to take the current Silver, and work through all the
changes in the branches currently being maintained in SVN
(build-improvements and wh-sandbox in particular) in a GIT repository
(thus "recreating" the revision history in GIT) would it be possible to
switch to a broader use of GIT?

I know SCMs are a bit of a religous issue, and I won't try to go into
which is "best", but I think the development model GIT uses may be a
fairly good match to the Axiom project.  If the revision histories were
re-created in GIT for the various branches, would that overcome the
practical difficulty in switching?

I don't say I know GIT well enough to do it "correctly" yet, but if we
can work in the same system it should (hopefully) be a lot easier to
address these branching issues.  In the process of doing the conversion
perhaps some of the branches can be brought closer together and some
good GIT for Axiom tutorials could be written.

If I were to attempt this (it would be a little while before I could
start, as my PC decided to give up the ghost and I'm having to rebuild)
would the key parties be interested enough to give the results a try? 
(Assuming sufficient quality of work, of course.)

I am aware that people may be too comfortable with their current tool
to want to switch to something else, and I understand if that's the
case - I'm just looking for something practical that can be done to
help keep the current diverging situation from continuing to diverge
more than necessary.

Cheers,
CY


       
____________________________________________________________________________________
Got a little couch potato? 
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz