Uncommit part or all of a local changeset Unified command to show various repository informationĪllow sparse checkouts of the working directoryĬommand to split a changeset into smaller ones Generate release notes from commit messagesĪllows clones that leave the majority of file history on the server. Store some pushes in a remote blob store on the serverĭownload only part of the history, see NarrowClonePlan Rewrite file content in changesets or working copy Yet another annotate implementation that might be faster Strip changesets and their descendants from historyĬherry-picking, rebasing and changeset rewritingĪllow to use shift_jis/big5 filenames on Windows.Īnnounce and browse repositories via zeroconf/bonjourĪpply working directory changes to changesetsīeautify log -G output by using Unicode characters Save and restore changes to the working directory Share repository history between multiple repos Recreates hardlinks between repository clones Purge all files and dirs in the repository that are not being tracked by Mercurial Send a collection of changesets as a series of patch emails Send email to subscribed addresses to notify repository changes Mercurial Patch Queues - manage changes as series of patches Use CVS like keyword expansion in tracked files Highlight syntax in the file revision view of hgwebĮdit, fold, drop changesets in the style of git rebase -interactive Graphical repository and history browser based on gitk Sign changesets and check signatures using GPG Try mapping git commands to Mercurial commands Integrates the file-monitoring program watchman with Mercurial to produce faster status results. Translate line-ending characters between working copy and repositoryĮxport repositories as git fast-import stream (advanced) Adds a new flag extras to commitĬonvert repositories from other SCMs into Mercurial (obsolete) Color output for the diff, status and qseries commands Show change statistics for mercurial operations per authorĪdvertise pre-generated bundles to seed clonesĬlose arbitrary heads without checking them out first Update Bugzilla entries when a bug id is referenced in a changeset hg/blackbox.log for post-mortem debugging Manage commit access to parts of a repo using control lists These extensions are maintained by the Mercurial project and are distributed together with Mercurial. # ditto, but no path was supplied for extension bazĮxtensions can often be configured further in an extension specific section in the same configuration file. # disabling extension bar residing in /path/to/extension/bar.py To explicitly disable an extension enabled in an hgrc of broader scope, prepend its path with !: NB: On Windows, if the path refers to a directory then the trailing backwards slash must currently be omitted due to issue4187. In the example above it was downloaded to ~/.hgext/. To get an extension which is not shipped with Mercurial, just download it to any place in your filesystem. py file or a folder containing _init_.py): You may also specify the full path to an extension (which may be either a. To enable the "foo" extension, either shipped with Mercurial or in the Python search path, create an entry for it in your hgrc, like this: Note that Mercurial explicitly does not provide a stable API for extension programmers, so it is up to their respective providers/maintainers to adapt them to API changes. To get help about an enabled extension, run ' hg help '. Extensions allow the integration of powerful new features directly into the Mercurial core.įeatures in extensions may not conform to Mercurial's usual standards for safety, reliability, and ease of use.īuilt-in help on extensions is available with ' hg help extensions'. Advanced users of Mercurial can be aided with the use of Mercurial extensions. Mercurial is designed to offer a small, safe, and easy to use command set which is powerful enough for most users. Authentication, access control and logging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |