Important changes CVS contributors must make for the great CVS -> Git migration

January 30th, 2011

If you are a contributor with CVS access, please read this important announcement! We need you to make some changes to your user profile by February 13, 2011.

For those who don’t know, we’re migrating’s version control system from CVS to Git very soon! Git associates commits with a name and e-mail address, rather than a username as in CVS.

In order to ensure that you are properly credited for both your legacy and future contributions post-Git migration, please complete the following steps:

  1. Decide which e-mail address you want to use for your Git commits and update your profile accordingly. [instructions]
  2. Decide if you want to change your CVS username (which will be used for Git). If you do, respond at the issue listed below with your uid and desired Git username. [instructions]

Decide which e-mail address you want to use for your Git commits

It’s important to consider the question of which e-mail address to associate with your Git commits. While your e-mail addresses won’t ever be visible to others on, they can be viewed with git log commands and similar. So it’s generally a good idea to specify an e-mail address that you would be comfortable giving out to untrusted people. At the same time, it is a generally accepted practice in the wider Git world to use a real e-mail address for this data.

More information:

Decide if you want to change your CVS username

Your Git username on will be the same as your existing CVS account username unless you ask for it to be changed here: will use this Git username to generate URIs for sandbox projects you create (see for a summary of what sandbox projects will be). You will also use this as your SSH username when authenticating to with Git.
This is your only chance to change your Git username. Once it’s set, it’s permanent. By default, all existing CVS account holders will have a Git account created with the same username. So if you don’t like your CVS account name, now’s the time to act!

Some background information

In order to sync CVS usernames with Git usernames we’re deploying two new modules to

  • Multiple E-mail Addresses: Allows you to associate more than one e-mail address (e.g. the one you use on GitHub, the one you use on with your Drupal user account. All users’ e-mail addresses are now editable on an “E-mail addresses” sub-tab, rather than the main user edit page.
  • CVS Migration Prefs: Specifies to which e-mail address your legacy commits should be credited, once imported into Git. You can also choose a fake “no-reply” e-mail for all your legacy commits, in order to protect your privacy. If left untouched, this fake e-mail will be used. Your selection for legacy commit credit cannot be changed post-Git migration.

Please see the following handbook pages for detailed instructions: