On Tue, Feb 26, 2008 at 11:16:08AM +0100, Gerhard Killesreiter wrote:
Larry Garfield schrieb:
On Mon, 25 Feb 2008 15:44:56 -0500, Earnie Boyd <earnie@users.sourceforge.net> wrote:
Quoting Liam McDermott <liam@intermedia-online.com>:
Gerhard Killesreiter wrote:
What we coud do (as long as the relevant backend for the project module exists) is to move core development to git. There we are free of social reasons. This sounds like an excellent idea! The only problem is having to maintain two seperate version control systems at the same time. On a related point: if this works for core, would it not make sense to allow contrib maintainers the option to use Git instead of CVS?
Make Git optional and contrib maintainers can move over at their own speed. If/when a Windows GUI client becomes available for example. It would also be interesting to see how many people stick with CVS, if nearly everyone switches their modules/themes to Git, CVS could be deprecated pretty quickly.
Just throwing some ideas around. Sorry if this has all been said before. :) Nice idea. Now all that is left is the work to help Derek with making the transition for the project module.
Except for those people who do checkout anonymously from core for various reasons and don't want to have to deal with yet another RCS with completely different semantics...
*raises hand*
Well, there could be a read-only cvs (or svn) mirror of core... :p
Cheers, Gerhard
Ya, we could use the git-cvsserver to still have anon-cvs access for core. -- Narayan Newton Database Administrator OSU Open Source Lab GA Member Drupal Association