[SM-Discuss] SCM perforce replacement
dkowis at shlrm.org
Thu Mar 16 10:32:03 EST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Andrew "ruskie" Levstik wrote:
> I see nothing wrong with having multiple SCM's.
My only problem with having multiple SCM's is that if a new developer
wants to contribute, but isn't sure where they want to contribute, they
will have to learn multiple SCM's and the commit methodologies applied
to each one. I, personally, would find that annoying. I would like to
see the entire project using one SCM. Keeps it simple, keeps the code
together and in the same format (backend storage). Less to manage.
ISO Team Lead - www.sourcemage.org
Source Mage GNU/Linux
Progress isn't made by early risers. It's made by lazy men trying to
find easier ways to do something.
- Robert Heinlein
Any sufficiently advanced technology is indistinguishable from magic.
- Arthur C. Clarke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
-----END PGP SIGNATURE-----
More information about the SM-Discuss