Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Mercurial commands and configuration in the DCDT project.

Global Configuration

The .hgrc file is for Mercurial configuration. On Windows it is in the .hg directory in the top level of a local repository clone, and on Linux/Mac it is in file ~/.hghgrc.

In Windows, Mercurial is also configured with %USERPROFILE%\Mercurial.ini.

You can setup authentication rules for all googlecode repositories in your global .hgrc file like this:

Code Block
languagenone
linenumberstrue
[auth]
googlecode.schemes=https
googlecode.prefix = code.google.com
googlecode.username = <your username>
googlecode.password = <your password>

 

Since development is done on a personal branch, changesets initially need to be pushed to one's personal repository. It is therefore best practice to set the default push location as a personal repository. Set the default path as the URL of your personal repository., but also need a facility to easily pull from the main DCDT repository, and this can be done with this configuration in <DCDT local root>/.hg/hgrc file:

Code Block
linenumberstrue
[paths]
Code Block
default = https://code.google.com/r/<personal_repo_name>/

 

Interacting with the main repository

Pull from the main repository just before a code review

Code Block
hg pull<your clone>/
dcdt = https://code.google.com/p/direct-certificate-discovery-tool/

Interacting with the main repository

Pull from the main repository after every changeset is pushed to it, in order to make sure your workspace/clone doesn't fall behind:

Code Block
hg pull dcdt

Push to the main repository after all code reviews are donecompleted:

Code Block
hg push -r <revision[s]> https://code.google.com/p/direct-certificate-discovery-tool/dcdt