UNH AI Wiki

 

Configuring Mercurial

Page history last edited by eaburns 2 wks ago

Who are you?

You can tell mercurial in a special section in your ~/.hgrc file:

[ui]
username = Jon Doe <jon.doe@somemail.com>

Trusting the AI group users

For some reason mercurial gives warnings if you get changes from the other AI group users.  You can explicitly say to trust this group using the following section:

[trusted]
users = *
groups = ai

Extensions

Mercurial has some useful extensions that you may want to enable.  To enable an extension, you need to add a section to your ~/.hgrc file.   Here is what my extensions section  looks like:

[extensions]
hgext.hgk =
hgext.grahplog =
hgext.fetch

 

There are a few extensions enabled:

  1. hgext.hgk enables the 'hg view' command which gives a gtk based graphical log/revision tree viewer.  This is very handy when you need to look at revision history.
  2. hgext.graphlog enables the 'hg glog' command which depicts an ASCII graphic of the revision tree next to a commit log.
  3. hgext.fetch enables the 'hg fetch' command.  Fetch is a convenient way to pull-and-possibly-merge-and-commit.  If there were both remote and local changes, the typical dance would be: hg pull; hg merge; hg commit -m "Merge";  This isn't very appealing however, not only because it is three commands but because the commit message is meaningless.  Fetch will roll these three commands into one and gives a more meaningful or at very least standardized commit message.

Comments (0)

You don't have permission to comment on this page.