Also, be sure that any system-installed /etc/mercurial/hgrc doesn't already activate these extensions (in particular, some systems activate the mq extension by default) funky things can happen on some versions of Mercurial if an extension is activated multiple times, particularly if a different syntax is used to enable it.Ī lot of time is spent committing your own changes locally, pulling down new changesets from the public repositories, merging the local changesets with the remote changesets if necessary, and finally updating the local working copy: hg ci hg pull hg merge hg ci hg update. Most, if not all, the ones I have as examples here ship standard with Mercurial however, some are new additions that may not be available by default in versions of Mercurial prior to 1.0. Obviously, in order to use extensions, they have to be installed. Mercurial is architected as a core set of functionality in the main program, and a variety of useful and even important tools that are provided as extensions, so you can pick and choose which pieces you really want (or add your own). The section is a means for you to tell Mercurial which extensions should be made available for use by default. See the next section for information about the glog and fetch commands. I prefer the "compact" changelog style over the default one, but YMMV. The section is where you can specify default arguments that are assumed whenever a particular command is used. It's a good idea to create a test repository with Mercurial with hg init foo, and then start checking some things into it ( cd foo vim bar hg add bar hg ci), to verify that the commit logs look right. I don't actually have username set in my ~/.hgrc, as I have EMAIL set and exported in my ~/.bashrc. That may be the better option, as other tools (notably, editors that have support for adding ChangeLog entries, which is an important part of hacking on GNU sources) will understand EMAIL. If this value is not set, Mercurial will use the EMAIL environment variable, if that's set. I can't accept changesets as-is if they don't have a usable user id.
Setting username tells Mercurial what identity to associate your commits with. Here's a sample ~/.hgrc file:Įnabling verbose output is generally just a prudent thing to do. This page is intended to help developers get started with using Mercurial in GNU Wget development.Īfter you've installed Mercurial, it's a good idea to set up some basic configuration settings. This page is not intended to replace the resources available on that site, and to use Mercurial to its fullest, you're best off if you start reading over there.
#TORTOISEHG USER FIXED IN HGRC HOW TO#
It includes a link to a free book-in-progress on using Mercurial, as well as other documentation, which contain a wealth of information on how to use Mercurial. The Mercurial wiki site is a good place to start for information on installing and using Mercurial.
0 kommentar(er)
