Alternative VCS mirrors of cvs.drupal.org
Though cvs.drupal.org is the official repository for Drupal development, some unofficial mirrors have been set up for users of version control systems other than CVS. While it is important to contribute your code back to Drupal's official repository, having a mirror available in your preferred version control system can be useful at times. With that in mind, below is a list of unofficial mirrors. Depending on the mirror, not all history or modules may be included. For more details, see the "about" link associated with each.
And before asking why Drupal is still on CVS, be sure to read Why is Drupal still using CVS and how can I help change that?
Subversion
Maintainer: Dembach und Co.
Repository: http://subversible.com/svn/
About: Subversible
Maintainer: Advantage Labs
Repository: http://svn.advantagelabs.com/managed/
About: Advantage Labs SVN Repository Structure
Acquia also maintains a Subversion repository for the Acquia Drupal distribution.
Bazaar
Maintainer: Four Kitchens Studios
Repository: bzr://vcs.fourkitchens.com/
About: Using Bazaar to collaborate with other patch developers and Using Bazaar to work on Drupal core patches
Maintainer: Launchpad
Repository: lp:drupal
About: Bazaar (a non-CVS version control system)
Git
The full mirror of the whole drupal.org CVS (core and contributions) is available at http://git.drupalfr.org
For core, please use the github repository, that is pulled from git.drupalfr.org:
Maintainer: Mikkel Høgh
Repository: git://github.com/drupal/drupal.git
About: A Git mirror for Drupal CVS
Mercurial
Maintainer: Michael Prasuhn
Repository: http://hg.shomeya.com/drupal-7/
About: Coming soon!
Only one git repo please...
Since Mikkel's git repository is the first that has been created and Damien's repository is currently unreachable, I would strongly recommend we all stick only to Mikkel's repository for now. That doesn't mean we can't have our own repositories, but they should be clones of Mikkel's (unless that repository shows some deficiency I'm not yet aware of, and that should be reported).
Regardless of the actual one chosen, we should really agree on a single git repository to sync with. This will ensure that every CVS commit has a single git commit associated with it in the "global git history".
I would hate to think what would happen if I would try to merge with another git branch that has been created from another git-cvsimport...
Good idea...
... but no need to go hatin' on Damien's repo. :) I had the opposite experience this spring sometime - Mikkel's repo hadn't updated itself for three weeks, and Damien's was humming away nicely. Either way, I agree it would be nice if everyone could merge their git efforts.
~ Katherine
Mikl's github repo is
Mikl's github repo is actually pulling from Damien's - so the commit IDs match.
---
Work: Acquia