mercurial-scm/hg: comparison mercurial/commands.py

equal deleted inserted replaced

-:d98cef25b5af
+:16f4cfc69e4f
 # Commands start here, listed alphabetically
 def add(ui, repo, *pats, **opts):
 """add the specified files on the next commit
-Schedule files to be version controlled and added to the repository.
+Schedule files to be version controlled and added to the
+repository.
-The files will be added to the repository at the next commit. To undo an
-add before that, see hg forget.
+The files will be added to the repository at the next commit. To
+undo an add before that, see hg forget.
 If no names are given, add all files to the repository.
 """
 bad = []
 return bad and 1 or 0
 def addremove(ui, repo, *pats, **opts):
 """add all new files, delete all missing files
-Add all new files and remove all missing files from the repository.
+Add all new files and remove all missing files from the
+repository.
-New files are ignored if they match any of the patterns in .hgignore. As
-with add, these changes take effect at the next commit.
+New files are ignored if they match any of the patterns in
+.hgignore. As with add, these changes take effect at the next
-Use the -s/--similarity option to detect renamed files. With a parameter
+commit.
-greater than 0, this compares every removed file with every added file and
-records those similar enough as renames. This option takes a percentage
+Use the -s/--similarity option to detect renamed files. With a
-between 0 (disabled) and 100 (files must be identical) as its parameter.
+parameter greater than 0, this compares every removed file with
-Detecting renamed files this way can be expensive.
+every added file and records those similar enough as renames. This
+option takes a percentage between 0 (disabled) and 100 (files must
+be identical) as its parameter. Detecting renamed files this way
+can be expensive.
 """
 try:
 sim = float(opts.get('similarity') or 0)
 except ValueError:
 raise util.Abort(_('similarity must be a number'))
 return cmdutil.addremove(repo, pats, opts, similarity=sim/100.)
 def annotate(ui, repo, *pats, **opts):
 """show changeset information by line for each file
-List changes in files, showing the revision id responsible for each line
+List changes in files, showing the revision id responsible for
+each line
-This command is useful for discovering when a change was made and by whom.
+This command is useful for discovering when a change was made and
-Without the -a/--text option, annotate will avoid processing files it
+by whom.
-detects as binary. With -a, annotate will annotate the file anyway,
-although the results will probably be neither useful nor desirable.
+Without the -a/--text option, annotate will avoid processing files
+it detects as binary. With -a, annotate will annotate the file
+anyway, although the results will probably be neither useful
+nor desirable.
 """
 datefunc = ui.quiet and util.shortdate or util.datestr
 getdate = util.cachefunc(lambda x: datefunc(x[0].date()))
 if not pats:
 ui.write("%s: %s" % (" ".join(p), l[1]))
 def archive(ui, repo, dest, **opts):
 '''create an unversioned archive of a repository revision
-By default, the revision used is the parent of the working directory; use
+By default, the revision used is the parent of the working
--r/--rev to specify a different revision.
+directory; use -r/--rev to specify a different revision.
-To specify the type of archive to create, use -t/--type. Valid types are::
+To specify the type of archive to create, use -t/--type. Valid
+types are::
 "files" (default): a directory full of files
 "tar": tar archive, uncompressed
 "tbz2": tar archive, compressed using bzip2
 "tgz": tar archive, compressed using gzip
 "uzip": zip archive, uncompressed
 "zip": zip archive, compressed using deflate
-The exact name of the destination archive or directory is given using a
+The exact name of the destination archive or directory is given
-format string; see 'hg help export' for details.
+using a format string; see 'hg help export' for details.
-Each member added to an archive file has a directory prefix prepended. Use
+Each member added to an archive file has a directory prefix
--p/--prefix to specify a format string for the prefix. The default is the
+prepended. Use -p/--prefix to specify a format string for the
-basename of the archive, with suffixes removed.
+prefix. The default is the basename of the archive, with suffixes
+removed.
 '''
 ctx = repo[opts.get('rev')]
 if not ctx:
 raise util.Abort(_('no working directory: please specify a revision'))
 matchfn, prefix)
 def backout(ui, repo, node=None, rev=None, **opts):
 '''reverse effect of earlier changeset
-Commit the backed out changes as a new changeset. The new changeset is a
+Commit the backed out changes as a new changeset. The new
-child of the backed out changeset.
+changeset is a child of the backed out changeset.
-If you backout a changeset other than the tip, a new head is created. This
+If you backout a changeset other than the tip, a new head is
-head will be the new tip and you should merge this backout changeset with
+created. This head will be the new tip and you should merge this
-another head.
+backout changeset with another head.
-The --merge option remembers the parent of the working directory before
+The --merge option remembers the parent of the working directory
-starting the backout, then merges the new head with that changeset
+before starting the backout, then merges the new head with that
-afterwards. This saves you from doing the merge by hand. The result of
+changeset afterwards. This saves you from doing the merge by hand.
-this merge is not committed, as with a normal merge.
+The result of this merge is not committed, as with a normal merge.
 See 'hg help dates' for a list of formats valid for -d/--date.
 '''
 if rev and node:
 raise util.Abort(_("please specify just one revision"))
 def bisect(ui, repo, rev=None, extra=None, command=None,
 reset=None, good=None, bad=None, skip=None, noupdate=None):
 """subdivision search of changesets
-This command helps to find changesets which introduce problems. To use,
+This command helps to find changesets which introduce problems. To
-mark the earliest changeset you know exhibits the problem as bad, then
+use, mark the earliest changeset you know exhibits the problem as
-mark the latest changeset which is free from the problem as good. Bisect
+bad, then mark the latest changeset which is free from the problem
-will update your working directory to a revision for testing (unless the
+as good. Bisect will update your working directory to a revision
--U/--noupdate option is specified). Once you have performed tests, mark
+for testing (unless the -U/--noupdate option is specified). Once
-the working directory as good or bad, and bisect will either update to
+you have performed tests, mark the working directory as good or
-another candidate changeset or announce that it has found the bad
+bad, and bisect will either update to another candidate changeset
-revision.
+or announce that it has found the bad revision.
-As a shortcut, you can also use the revision argument to mark a revision
+As a shortcut, you can also use the revision argument to mark a
-as good or bad without checking it out first.
+revision as good or bad without checking it out first.
-If you supply a command, it will be used for automatic bisection. Its exit
+If you supply a command, it will be used for automatic bisection.
-status will be used to mark revisions as good or bad: status 0 means good,
+Its exit status will be used to mark revisions as good or bad:
-125 means to skip the revision, 127 (command not found) will abort the
+status 0 means good, 125 means to skip the revision, 127
-bisection, and any other non-zero exit status means the revision is bad.
+(command not found) will abort the bisection, and any other
+non-zero exit status means the revision is bad.
 """
 def print_result(nodes, good):
 displayer = cmdutil.show_changeset(ui, repo, {})
 if len(nodes) == 1:
 # narrowed it down to a single revision
 return hg.clean(repo, node)
 def branch(ui, repo, label=None, **opts):
 """set or show the current branch name
-With no argument, show the current branch name. With one argument, set the
+With no argument, show the current branch name. With one argument,
-working directory branch name (the branch will not exist in the repository
+set the working directory branch name (the branch will not exist
-until the next commit). Standard practice recommends that primary
+in the repository until the next commit). Standard practice
-development take place on the 'default' branch.
+recommends that primary development take place on the 'default'
+branch.
-Unless -f/--force is specified, branch will not let you set a branch name
-that already exists, even if it's inactive.
+Unless -f/--force is specified, branch will not let you set a
+branch name that already exists, even if it's inactive.
-Use -C/--clean to reset the working directory branch to that of the parent
-of the working directory, negating a previous branch change.
+Use -C/--clean to reset the working directory branch to that of
+the parent of the working directory, negating a previous branch
-Use the command 'hg update' to switch to an existing branch. Use 'hg
+change.
-commit --close-branch' to mark this branch as closed.
+Use the command 'hg update' to switch to an existing branch. Use
+'hg commit --close-branch' to mark this branch as closed.
 """
 if opts.get('clean'):
 label = repo[None].parents()[0].branch()
 repo.dirstate.setbranch(label)
 ui.write("%s\n" % encoding.tolocal(repo.dirstate.branch()))
 def branches(ui, repo, active=False, closed=False):
 """list repository named branches
-List the repository's named branches, indicating which ones are inactive.
+List the repository's named branches, indicating which ones are
-If -c/--closed is specified, also list branches which have been marked
+inactive. If -c/--closed is specified, also list branches which have
-closed (see hg commit --close-branch).
+been marked closed (see hg commit --close-branch).
-If -a/--active is specified, only show active branches. A branch is
+If -a/--active is specified, only show active branches. A branch
-considered active if it contains repository heads.
+is considered active if it contains repository heads.
 Use the command 'hg update' to switch to an existing branch.
 """
 hexfunc = ui.debugflag and hex or short
 ui.write("%s %s:%s%s\n" % data)
 def bundle(ui, repo, fname, dest=None, **opts):
 """create a changegroup file
-Generate a compressed changegroup file collecting changesets not known to
+Generate a compressed changegroup file collecting changesets not
-be in another repository.
+known to be in another repository.
-If no destination repository is specified the destination is assumed to
+If no destination repository is specified the destination is
-have all the nodes specified by one or more --base parameters. To create a
+assumed to have all the nodes specified by one or more --base
-bundle containing all changesets, use -a/--all (or --base null).
+parameters. To create a bundle containing all changesets, use
+-a/--all (or --base null).
-You can change compression method with the -t/--type option. The available
-compression methods are: none, bzip2, and gzip (by default, bundles are
+You can change compression method with the -t/--type option.
-compressed using bzip2).
+The available compression methods are: none, bzip2, and
+gzip (by default, bundles are compressed using bzip2).
-The bundle file can then be transferred using conventional means and
-applied to another repository with the unbundle or pull command. This is
+The bundle file can then be transferred using conventional means
-useful when direct push and pull are not available or when exporting an
+and applied to another repository with the unbundle or pull
-entire repository is undesirable.
+command. This is useful when direct push and pull are not
+available or when exporting an entire repository is undesirable.
-Applying bundles preserves all changeset contents including permissions,
-copy/rename information, and revision history.
+Applying bundles preserves all changeset contents including
+permissions, copy/rename information, and revision history.
 """
 revs = opts.get('rev') or None
 if revs:
 revs = [repo.lookup(rev) for rev in revs]
 if opts.get('all'):
 changegroup.writebundle(cg, fname, bundletype)
 def cat(ui, repo, file1, *pats, **opts):
 """output the current or given revision of files
-Print the specified files as they were at the given revision. If no
+Print the specified files as they were at the given revision. If
-revision is given, the parent of the working directory is used, or tip if
+no revision is given, the parent of the working directory is used,
-no revision is checked out.
+or tip if no revision is checked out.
-Output may be to a file, in which case the name of the file is given using
+Output may be to a file, in which case the name of the file is
-a format string. The formatting rules are the same as for the export
+given using a format string. The formatting rules are the same as
-command, with the following additions::
+for the export command, with the following additions::
 %s   basename of file being printed
 %d   dirname of file being printed, or '.' if in repository root
 %p   root-relative path name of file being printed
 """
 def clone(ui, source, dest=None, **opts):
 """make a copy of an existing repository
 Create a copy of an existing repository in a new directory.
-If no destination directory name is specified, it defaults to the basename
+If no destination directory name is specified, it defaults to the
-of the source.
+basename of the source.
-The location of the source is added to the new repository's .hg/hgrc file,
+The location of the source is added to the new repository's
-as the default to be used for future pulls.
+.hg/hgrc file, as the default to be used for future pulls.
-If you use the -r/--rev option to clone up to a specific revision, no
+If you use the -r/--rev option to clone up to a specific revision,
-subsequent revisions (including subsequent tags) will be present in the
+no subsequent revisions (including subsequent tags) will be
-cloned repository. This option implies --pull, even on local repositories.
+present in the cloned repository. This option implies --pull, even
+on local repositories.
-By default, clone will check out the head of the 'default' branch. If the
--U/--noupdate option is used, the new clone will contain only a repository
+By default, clone will check out the head of the 'default' branch.
-(.hg) and no working copy (the working copy parent is the null revision).
+If the -U/--noupdate option is used, the new clone will contain
+only a repository (.hg) and no working copy (the working copy
+parent is the null revision).
 See 'hg help urls' for valid source format details.
 It is possible to specify an ssh:// URL as the destination, but no
-.hg/hgrc and working directory will be created on the remote side. Please
+.hg/hgrc and working directory will be created on the remote side.
-see 'hg help urls' for important details about ssh:// URLs.
+Please see 'hg help urls' for important details about ssh:// URLs.
-For efficiency, hardlinks are used for cloning whenever the source and
+For efficiency, hardlinks are used for cloning whenever the source
-destination are on the same filesystem (note this applies only to the
+and destination are on the same filesystem (note this applies only
-repository data, not to the checked out files). Some filesystems, such as
+to the repository data, not to the checked out files). Some
-AFS, implement hardlinking incorrectly, but do not report errors. In these
+filesystems, such as AFS, implement hardlinking incorrectly, but
-cases, use the --pull option to avoid hardlinking.
+do not report errors. In these cases, use the --pull option to
+avoid hardlinking.
-In some cases, you can clone repositories and checked out files using full
-hardlinks with ::
+In some cases, you can clone repositories and checked out files
+using full hardlinks with ::
 $ cp -al REPO REPOCLONE
-This is the fastest way to clone, but it is not always safe. The operation
+This is the fastest way to clone, but it is not always safe. The
-is not atomic (making sure REPO is not modified during the operation is up
+operation is not atomic (making sure REPO is not modified during
-to you) and you have to make sure your editor breaks hardlinks (Emacs and
+the operation is up to you) and you have to make sure your editor
-most Linux Kernel tools do so). Also, this is not compatible with certain
+breaks hardlinks (Emacs and most Linux Kernel tools do so). Also,
-extensions that place their metadata under the .hg directory, such as mq.
+this is not compatible with certain extensions that place their
+metadata under the .hg directory, such as mq.
 """
 hg.clone(cmdutil.remoteui(ui, opts), source, dest,
 pull=opts.get('pull'),
 stream=opts.get('uncompressed'),
 rev=opts.get('rev'),
 def commit(ui, repo, *pats, **opts):
 """commit the specified files or all outstanding changes
 Commit changes to the given files into the repository. Unlike a
-centralized RCS, this operation is a local operation. See hg push for a
+centralized RCS, this operation is a local operation. See hg push
-way to actively distribute your changes.
+for a way to actively distribute your changes.
-If a list of files is omitted, all changes reported by "hg status" will be
+If a list of files is omitted, all changes reported by "hg status"
-committed.
+will be committed.
-If you are committing the result of a merge, do not provide any filenames
+If you are committing the result of a merge, do not provide any
-or -I/-X filters.
+filenames or -I/-X filters.
-If no commit message is specified, the configured editor is started to
+If no commit message is specified, the configured editor is
-prompt you for a message.
+started to prompt you for a message.
 See 'hg help dates' for a list of formats valid for -d/--date.
 """
 extra = {}
 if opts.get('close_branch'):
 ui.write(_('committed changeset %d:%s\n') % (rev, short(node)))
 def copy(ui, repo, *pats, **opts):
 """mark files as copied for the next commit
-Mark dest as having copies of source files. If dest is a directory, copies
+Mark dest as having copies of source files. If dest is a
-are put in that directory. If dest is a file, the source must be a single
+directory, copies are put in that directory. If dest is a file,
-file.
+the source must be a single file.
-By default, this command copies the contents of files as they exist in the
+By default, this command copies the contents of files as they
-working directory. If invoked with -A/--after, the operation is recorded,
+exist in the working directory. If invoked with -A/--after, the
-but no copying is performed.
+operation is recorded, but no copying is performed.
-This command takes effect with the next commit. To undo a copy before
+This command takes effect with the next commit. To undo a copy
-that, see hg revert.
+before that, see hg revert.
 """
 wlock = repo.wlock(False)
 try:
 return cmdutil.copy(ui, repo, pats, opts)
 finally:
 def showconfig(ui, repo, *values, **opts):
 """show combined config settings from all hgrc files
 With no arguments, print names and values of all config items.
-With one argument of the form section.name, print just the value of that
+With one argument of the form section.name, print just the value
-config item.
+of that config item.
-With multiple arguments, print names and values of all config items with
+With multiple arguments, print names and values of all config
-matching section names.
+items with matching section names.
-With --debug, the source (filename and line number) is printed for each
+With --debug, the source (filename and line number) is printed
-config item.
+for each config item.
 """
 untrusted = bool(opts.get('untrusted'))
 if values:
 if len([v for v in values if '.' in v]) > 1:
 ui.write('%s=%s\n' % (sectname, value))
 def debugsetparents(ui, repo, rev1, rev2=None):
 """manually set the parents of the current working directory
-This is useful for writing repository conversion tools, but should be used
+This is useful for writing repository conversion tools, but should
-with care.
+be used with care.
 """
 if not rev2:
 rev2 = hex(nullid)
 Show differences between revisions for the specified files.
 Differences between files are shown using the unified diff format.
-NOTE: diff may generate unexpected results for merges, as it will default
+NOTE: diff may generate unexpected results for merges, as it will
-to comparing against the working directory's first parent changeset if no
+default to comparing against the working directory's first parent
-revisions are specified.
+changeset if no revisions are specified.
-When two revision arguments are given, then changes are shown between
+When two revision arguments are given, then changes are shown
-those revisions. If only one revision is specified then that revision is
+between those revisions. If only one revision is specified then
-compared to the working directory, and, when no revisions are specified,
+that revision is compared to the working directory, and, when no
-the working directory files are compared to its parent.
+revisions are specified, the working directory files are compared
+to its parent.
-Without the -a/--text option, diff will avoid generating diffs of files it
-detects as binary. With -a, diff will generate a diff anyway, probably
+Without the -a/--text option, diff will avoid generating diffs of
-with undesirable results.
+files it detects as binary. With -a, diff will generate a diff
+anyway, probably with undesirable results.
-Use the -g/--git option to generate diffs in the git extended diff format.
-For more information, read 'hg help diffs'.
+Use the -g/--git option to generate diffs in the git extended diff
+format. For more information, read 'hg help diffs'.
 """
 revs = opts.get('rev')
 change = opts.get('change')
 def export(ui, repo, *changesets, **opts):
 """dump the header and diffs for one or more changesets
 Print the changeset header and diffs for one or more revisions.
-The information shown in the changeset header is: author, changeset hash,
+The information shown in the changeset header is: author,
-parent(s) and commit comment.
+changeset hash, parent(s) and commit comment.
-NOTE: export may generate unexpected diff output for merge changesets, as
+NOTE: export may generate unexpected diff output for merge
-it will compare the merge changeset against its first parent only.
+changesets, as it will compare the merge changeset against its
+first parent only.
-Output may be to a file, in which case the name of the file is given using
-a format string. The formatting rules are as follows::
+Output may be to a file, in which case the name of the file is
+given using a format string. The formatting rules are as follows::
 %%   literal "%" character
 %H   changeset hash (40 bytes of hexadecimal)
 %N   number of patches being generated
 %R   changeset revision number
 %b   basename of the exporting repository
 %h   short-form changeset hash (12 bytes of hexadecimal)
 %n   zero-padded sequence number, starting at 1
 %r   zero-padded changeset revision number
-Without the -a/--text option, export will avoid generating diffs of files
+Without the -a/--text option, export will avoid generating diffs
-it detects as binary. With -a, export will generate a diff anyway,
+of files it detects as binary. With -a, export will generate a
-probably with undesirable results.
+diff anyway, probably with undesirable results.
-Use the -g/--git option to generate diffs in the git extended diff format.
+Use the -g/--git option to generate diffs in the git extended diff
-See 'hg help diffs' for more information.
+format. See 'hg help diffs' for more information.
-With the --switch-parent option, the diff will be against the second
+With the --switch-parent option, the diff will be against the
-parent. It can be useful to review a merge.
+second parent. It can be useful to review a merge.
 """
 if not changesets:
 raise util.Abort(_("export requires at least one changeset"))
 revs = cmdutil.revrange(repo, changesets)
 if len(revs) > 1:
 opts=patch.diffopts(ui, opts))
 def forget(ui, repo, *pats, **opts):
 """forget the specified files on the next commit
-Mark the specified files so they will no longer be tracked after the next
+Mark the specified files so they will no longer be tracked
-commit.
+after the next commit.
-This only removes files from the current branch, not from the entire
+This only removes files from the current branch, not from the
-project history, and it does not delete them from the working directory.
+entire project history, and it does not delete them from the
+working directory.
 To undo a forget before the next commit, see hg add.
 """
 if not pats:
 """search for a pattern in specified files and revisions
 Search revisions of files for a regular expression.
 This command behaves differently than Unix grep. It only accepts
-Python/Perl regexps. It searches repository history, not the working
+Python/Perl regexps. It searches repository history, not the
-directory. It always prints the revision number in which a match appears.
+working directory. It always prints the revision number in which a
+match appears.
-By default, grep only prints output for the first revision of a file in
-which it finds a match. To get it to print every revision that contains a
+By default, grep only prints output for the first revision of a
-change in match status ("-" for a match that becomes a non-match, or "+"
+file in which it finds a match. To get it to print every revision
-for a non-match that becomes a match), use the --all flag.
+that contains a change in match status ("-" for a match that
+becomes a non-match, or "+" for a non-match that becomes a match),
+use the --all flag.
 """
 reflags = 0
 if opts.get('ignore_case'):
 reflags |= re.I
 try:
 def heads(ui, repo, *branchrevs, **opts):
 """show current repository heads or show branch heads
 With no arguments, show all repository head changesets.
-Repository "heads" are changesets that don't have child changesets. They
+Repository "heads" are changesets that don't have child
-are where development generally takes place and are the usual targets for
+changesets. They are where development generally takes place and
-update and merge operations.
+are the usual targets for update and merge operations.
-If one or more REV is given, the "branch heads" will be shown for the
+If one or more REV is given, the "branch heads" will be shown for
-named branch associated with that revision. The name of the branch is
+the named branch associated with that revision. The name of the
-called the revision's branch tag.
+branch is called the revision's branch tag.
-Branch heads are revisions on a given named branch that do not have any
+Branch heads are revisions on a given named branch that do not have
-descendants on the same branch. A branch head could be a true head or it
+any descendants on the same branch. A branch head could be a true head
-could be the last changeset on a branch before a new branch was created.
+or it could be the last changeset on a branch before a new branch
-If none of the branch heads are true heads, the branch is considered
+was created. If none of the branch heads are true heads, the branch
-inactive. If -c/--closed is specified, also show branch heads marked
+is considered inactive. If -c/--closed is specified, also show branch
-closed (see hg commit --close-branch).
+heads marked closed (see hg commit --close-branch).
-If STARTREV is specified only those heads (or branch heads) that are
+If STARTREV is specified only those heads (or branch heads) that
-descendants of STARTREV will be displayed.
+are descendants of STARTREV will be displayed.
 """
 if opts.get('rev'):
 start = repo.lookup(opts['rev'])
 else:
 start = None
 def help_(ui, name=None, with_version=False):
 """show help for a given topic or a help overview
 With no arguments, print a list of commands with short help messages.
-Given a topic, extension, or command name, print help for that topic.
+Given a topic, extension, or command name, print help for that
-"""
+topic."""
 option_lists = []
 textwidth = util.termwidth() - 2
 def addglobalopts(aliases):
 if ui.verbose:
 def identify(ui, repo, source=None,
 rev=None, num=None, id=None, branch=None, tags=None):
 """identify the working copy or specified revision
-With no revision, print a summary of the current state of the repository.
+With no revision, print a summary of the current state of the
+repository.
-Specifying a path to a repository root or Mercurial bundle will cause
-lookup to operate on that repository/bundle.
+Specifying a path to a repository root or Mercurial bundle will
+cause lookup to operate on that repository/bundle.
-This summary identifies the repository state using one or two parent hash
-identifiers, followed by a "+" if there are uncommitted changes in the
+This summary identifies the repository state using one or two
-working directory, a list of tags for this revision and a branch name for
+parent hash identifiers, followed by a "+" if there are
-non-default branches.
+uncommitted changes in the working directory, a list of tags for
+this revision and a branch name for non-default branches.
 """
 if not repo and not source:
 raise util.Abort(_("There is no Mercurial repository here "
 "(.hg not found)"))
 def import_(ui, repo, patch1, *patches, **opts):
 """import an ordered set of patches
 Import a list of patches and commit them individually.
-If there are outstanding changes in the working directory, import will
+If there are outstanding changes in the working directory, import
-abort unless given the -f/--force flag.
+will abort unless given the -f/--force flag.
-You can import a patch straight from a mail message. Even patches as
+You can import a patch straight from a mail message. Even patches
-attachments work (to use the body part, it must have type text/plain or
+as attachments work (to use the body part, it must have type
-text/x-patch). From and Subject headers of email message are used as
+text/plain or text/x-patch). From and Subject headers of email
-default committer and commit message. All text/plain body parts before
+message are used as default committer and commit message. All
-first diff are added to commit message.
+text/plain body parts before first diff are added to commit
+message.
-If the imported patch was generated by hg export, user and description
-from patch override values from message headers and body. Values given on
+If the imported patch was generated by hg export, user and
-command line with -m/--message and -u/--user override these.
+description from patch override values from message headers and
+body. Values given on command line with -m/--message and -u/--user
-If --exact is specified, import will set the working directory to the
+override these.
-parent of each patch before applying it, and will abort if the resulting
-changeset has a different ID than the one recorded in the patch. This may
+If --exact is specified, import will set the working directory to
-happen due to character set problems or other deficiencies in the text
+the parent of each patch before applying it, and will abort if the
-patch format.
+resulting changeset has a different ID than the one recorded in
+the patch. This may happen due to character set problems or other
-With -s/--similarity, hg will attempt to discover renames and copies in
+deficiencies in the text patch format.
-the patch in the same way as 'addremove'.
+With -s/--similarity, hg will attempt to discover renames and
-To read a patch from standard input, use "-" as the patch name. If a URL
+copies in the patch in the same way as 'addremove'.
-is specified, the patch will be downloaded from it. See 'hg help dates'
-for a list of formats valid for -d/--date.
+To read a patch from standard input, use "-" as the patch name. If
+a URL is specified, the patch will be downloaded from it.
+See 'hg help dates' for a list of formats valid for -d/--date.
 """
 patches = (patch1,) + patches
 date = opts.get('date')
 if date:
 release(lock, wlock)
 def incoming(ui, repo, source="default", **opts):
 """show new changesets found in source
-Show new changesets found in the specified path/URL or the default pull
+Show new changesets found in the specified path/URL or the default
-location. These are the changesets that would have been pulled if a pull
+pull location. These are the changesets that would have been pulled
-at the time you issued this command.
+if a pull at the time you issued this command.
-For remote repository, using --bundle avoids downloading the changesets
+For remote repository, using --bundle avoids downloading the
-twice if the incoming is followed by a pull.
+changesets twice if the incoming is followed by a pull.
 See pull for valid source format details.
 """
 limit = cmdutil.loglimit(opts)
 source, revs, checkout = hg.parseurl(ui.expandpath(source), opts.get('rev'))
 os.unlink(cleanup)
 def init(ui, dest=".", **opts):
 """create a new repository in the given directory
-Initialize a new repository in the given directory. If the given directory
+Initialize a new repository in the given directory. If the given
-does not exist, it will be created.
+directory does not exist, it will be created.
 If no directory is given, the current directory is used.
-It is possible to specify an ssh:// URL as the destination. See 'hg help
+It is possible to specify an ssh:// URL as the destination.
-urls' for more information.
+See 'hg help urls' for more information.
 """
 hg.repository(cmdutil.remoteui(ui, opts), dest, create=1)
 def locate(ui, repo, *pats, **opts):
 """locate files matching specific patterns
-Print files under Mercurial control in the working directory whose names
+Print files under Mercurial control in the working directory whose
-match the given patterns.
+names match the given patterns.
 By default, this command searches all directories in the working
-directory. To search just the current directory and its subdirectories,
+directory. To search just the current directory and its
-use "--include .".
+subdirectories, use "--include .".
-If no patterns are given to match, this command prints the names of all
+If no patterns are given to match, this command prints the names
-files under Mercurial control in the working directory.
+of all files under Mercurial control in the working directory.
-If you want to feed the output of this command into the "xargs" command,
+If you want to feed the output of this command into the "xargs"
-use the -0 option to both this command and "xargs". This will avoid the
+command, use the -0 option to both this command and "xargs". This
-problem of "xargs" treating single filenames that contain whitespace as
+will avoid the problem of "xargs" treating single filenames that
-multiple filenames.
+contain whitespace as multiple filenames.
 """
 end = opts.get('print0') and '\0' or '\n'
 rev = opts.get('rev') or None
 ret = 1
 return ret
 def log(ui, repo, *pats, **opts):
 """show revision history of entire repository or files
-Print the revision history of the specified files or the entire project.
+Print the revision history of the specified files or the entire
+project.
-File history is shown without following rename or copy history of files.
-Use -f/--follow with a filename to follow history across renames and
+File history is shown without following rename or copy history of
-copies. --follow without a filename will only show ancestors or
+files. Use -f/--follow with a filename to follow history across
-descendants of the starting revision. --follow-first only follows the
+renames and copies. --follow without a filename will only show
-first parent of merge revisions.
+ancestors or descendants of the starting revision. --follow-first
+only follows the first parent of merge revisions.
-If no revision range is specified, the default is tip:0 unless --follow is
-set, in which case the working directory parent is used as the starting
+If no revision range is specified, the default is tip:0 unless
-revision.
+--follow is set, in which case the working directory parent is
+used as the starting revision.
 See 'hg help dates' for a list of formats valid for -d/--date.
-By default this command prints revision number and changeset id, tags,
+By default this command prints revision number and changeset id,
-non-trivial parents, user, date and time, and a summary for each commit.
+tags, non-trivial parents, user, date and time, and a summary for
-When the -v/--verbose switch is used, the list of changed files and full
+each commit. When the -v/--verbose switch is used, the list of
-commit message are shown.
+changed files and full commit message are shown.
 NOTE: log -p/--patch may generate unexpected diff output for merge
-changesets, as it will only compare the merge changeset against its first
+changesets, as it will only compare the merge changeset against
-parent. Also, only files different from BOTH parents will appear in
+its first parent. Also, only files different from BOTH parents
-files:.
+will appear in files:.
 """
 get = util.cachefunc(lambda r: repo[r].changeset())
 changeiter, matchfn = cmdutil.walkchangerevs(ui, repo, pats, get, opts)
 count += 1
 def manifest(ui, repo, node=None, rev=None):
 """output the current or given revision of the project manifest
-Print a list of version controlled files for the given revision. If no
+Print a list of version controlled files for the given revision.
-revision is given, the first parent of the working directory is used, or
+If no revision is given, the first parent of the working directory
-the null revision if no revision is checked out.
+is used, or the null revision if no revision is checked out.
 With -v, print file permissions, symlink and executable bits.
 With --debug, print file revision hashes.
 """
 ui.write("%s\n" % f)
 def merge(ui, repo, node=None, **opts):
 """merge working directory with another revision
-The current working directory is updated with all changes made in the
+The current working directory is updated with all changes made in
-requested revision since the last common predecessor revision.
+the requested revision since the last common predecessor revision.
-Files that changed between either parent are marked as changed for the
+Files that changed between either parent are marked as changed for
-next commit and a commit must be performed before any further updates to
+the next commit and a commit must be performed before any further
-the repository are allowed. The next commit will have two parents.
+updates to the repository are allowed. The next commit will have
+two parents.
-If no revision is specified, the working directory's parent is a head
-revision, and the current branch contains exactly one other head, the
+If no revision is specified, the working directory's parent is a
-other head is merged with by default. Otherwise, an explicit revision with
+head revision, and the current branch contains exactly one other
-which to merge with must be provided.
+head, the other head is merged with by default. Otherwise, an
+explicit revision with which to merge with must be provided.
 """
 if opts.get('rev') and node:
 raise util.Abort(_("please specify just one revision"))
 if not node:
 return hg.merge(repo, node, force=opts.get('force'))
 def outgoing(ui, repo, dest=None, **opts):
 """show changesets not found in destination
-Show changesets not found in the specified destination repository or the
+Show changesets not found in the specified destination repository
-default push location. These are the changesets that would be pushed if a
+or the default push location. These are the changesets that would
-push was requested.
+be pushed if a push was requested.
 See pull for valid destination format details.
 """
 limit = cmdutil.loglimit(opts)
 dest, revs, checkout = hg.parseurl(
 displayer.show(repo[n])
 def parents(ui, repo, file_=None, **opts):
 """show the parents of the working directory or revision
-Print the working directory's parent revisions. If a revision is given via
+Print the working directory's parent revisions. If a revision is
--r/--rev, the parent of that revision will be printed. If a file argument
+given via -r/--rev, the parent of that revision will be printed.
-is given, the revision in which the file was last changed (before the
+If a file argument is given, the revision in which the file was
-working directory revision or the argument to --rev if given) is printed.
+last changed (before the working directory revision or the
+argument to --rev if given) is printed.
 """
 rev = opts.get('rev')
 if rev:
 ctx = repo[rev]
 else:
 displayer.show(repo[n])
 def paths(ui, repo, search=None):
 """show aliases for remote repositories
-Show definition of symbolic path name NAME. If no name is given, show
+Show definition of symbolic path name NAME. If no name is given,
-definition of all available names.
+show definition of all available names.
-Path names are defined in the [paths] section of /etc/mercurial/hgrc and
+Path names are defined in the [paths] section of /etc/mercurial/hgrc
-$HOME/.hgrc. If run inside a repository, .hg/hgrc is used, too.
+and $HOME/.hgrc. If run inside a repository, .hg/hgrc is used, too.
 See 'hg help urls' for more information.
 """
 if search:
 for name, path in ui.configitems("paths"):
 def pull(ui, repo, source="default", **opts):
 """pull changes from the specified source
 Pull changes from a remote repository to a local one.
-This finds all changes from the repository at the specified path or URL
+This finds all changes from the repository at the specified path
-and adds them to a local repository (the current one unless -R is
+or URL and adds them to a local repository (the current one unless
-specified). By default, this does not update the copy of the project in
+-R is specified). By default, this does not update the copy of the
-the working directory.
+project in the working directory.
-Use hg incoming if you want to see what would have been added by a pull at
+Use hg incoming if you want to see what would have been added by a
-the time you issued this command. If you then decide to added those
+pull at the time you issued this command. If you then decide to
-changes to the repository, you should use pull -r X where X is the last
+added those changes to the repository, you should use pull -r X
-changeset listed by hg incoming.
+where X is the last changeset listed by hg incoming.
-If SOURCE is omitted, the 'default' path will be used. See 'hg help urls'
+If SOURCE is omitted, the 'default' path will be used.
-for more information.
+See 'hg help urls' for more information.
 """
 source, revs, checkout = hg.parseurl(ui.expandpath(source), opts.get('rev'))
 other = hg.repository(cmdutil.remoteui(repo, opts), source)
 ui.status(_('pulling from %s\n') % url.hidepassword(source))
 if revs:
 def push(ui, repo, dest=None, **opts):
 """push changes to the specified destination
 Push changes from the local repository to the given destination.
-This is the symmetrical operation for pull. It moves changes from the
+This is the symmetrical operation for pull. It moves changes from
-current repository to a different one. If the destination is local this is
+the current repository to a different one. If the destination is
-identical to a pull in that directory from the current one.
+local this is identical to a pull in that directory from the
+current one.
 By default, push will refuse to run if it detects the result would
-increase the number of remote heads. This generally indicates the user
+increase the number of remote heads. This generally indicates the
-forgot to pull and merge before pushing.
+user forgot to pull and merge before pushing.
-If -r/--rev is used, the named revision and all its ancestors will be
+If -r/--rev is used, the named revision and all its ancestors will
-pushed to the remote repository.
+be pushed to the remote repository.
-Please see 'hg help urls' for important details about ssh:// URLs. If
+Please see 'hg help urls' for important details about ssh://
-DESTINATION is omitted, a default path will be used.
+URLs. If DESTINATION is omitted, a default path will be used.
 """
 dest, revs, checkout = hg.parseurl(
 ui.expandpath(dest or 'default-push', dest or 'default'), opts.get('rev'))
 other = hg.repository(cmdutil.remoteui(repo, opts), dest)
 ui.status(_('pushing to %s\n') % url.hidepassword(dest))
 def recover(ui, repo):
 """roll back an interrupted transaction
 Recover from an interrupted commit or pull.
-This command tries to fix the repository status after an interrupted
+This command tries to fix the repository status after an
-operation. It should only be necessary when Mercurial suggests it.
+interrupted operation. It should only be necessary when Mercurial
+suggests it.
 """
 if repo.recover():
 return hg.verify(repo)
 return 1
 def remove(ui, repo, *pats, **opts):
 """remove the specified files on the next commit
 Schedule the indicated files for removal from the repository.
-This only removes files from the current branch, not from the entire
+This only removes files from the current branch, not from the
-project history. -A/--after can be used to remove only files that have
+entire project history. -A/--after can be used to remove only
-already been deleted, -f/--force can be used to force deletion, and -Af
+files that have already been deleted, -f/--force can be used to
-can be used to remove files from the next revision without deleting them
+force deletion, and -Af can be used to remove files from the next
-from the working directory.
+revision without deleting them from the working directory.
-The following table details the behavior of remove for different file
+The following table details the behavior of remove for different
-states (columns) and option combinations (rows). The file states are Added
+file states (columns) and option combinations (rows). The file
-[A], Clean [C], Modified [M] and Missing [!] (as reported by hg status).
+states are Added [A], Clean [C], Modified [M] and Missing [!] (as
-The actions are Warn, Remove (from branch) and Delete (from disk)::
+reported by hg status). The actions are Warn, Remove (from branch)
+and Delete (from disk)::
 A  C  M  !
 none   W  RD W  R
 -f     R  RD RD R
 -A     W  W  W  R
 -Af    R  R  R  R
-This command schedules the files to be removed at the next commit. To undo
+This command schedules the files to be removed at the next commit.
-a remove before that, see hg revert.
+To undo a remove before that, see hg revert.
 """
 after, force = opts.get('after'), opts.get('force')
 if not pats and not after:
 raise util.Abort(_('no files specified'))
 repo.remove(remove, unlink=not after)
 def rename(ui, repo, *pats, **opts):
 """rename files; equivalent of copy + remove
-Mark dest as copies of sources; mark sources for deletion. If dest is a
+Mark dest as copies of sources; mark sources for deletion. If dest
-directory, copies are put in that directory. If dest is a file, there can
+is a directory, copies are put in that directory. If dest is a
-only be one source.
+file, there can only be one source.
-By default, this command copies the contents of files as they exist in the
+By default, this command copies the contents of files as they
-working directory. If invoked with -A/--after, the operation is recorded,
+exist in the working directory. If invoked with -A/--after, the
-but no copying is performed.
+operation is recorded, but no copying is performed.
-This command takes effect at the next commit. To undo a rename before
+This command takes effect at the next commit. To undo a rename
-that, see hg revert.
+before that, see hg revert.
 """
 wlock = repo.wlock(False)
 try:
 return cmdutil.copy(ui, repo, pats, opts, rename=True)
 finally:
 def resolve(ui, repo, *pats, **opts):
 """retry file merges from a merge or update
 This command will cleanly retry unresolved file merges using file
-revisions preserved from the last update or merge. To attempt to resolve
+revisions preserved from the last update or merge. To attempt to
-all unresolved files, use the -a/--all switch.
+resolve all unresolved files, use the -a/--all switch.
-If a conflict is resolved manually, please note that the changes will be
+If a conflict is resolved manually, please note that the changes
-overwritten if the merge is retried with resolve. The -m/--mark switch
+will be overwritten if the merge is retried with resolve. The
-should be used to mark the file as resolved.
+-m/--mark switch should be used to mark the file as resolved.
-This command also allows listing resolved files and manually indicating
+This command also allows listing resolved files and manually
-whether or not files are resolved. All files must be marked as resolved
+indicating whether or not files are resolved. All files must be
-before a commit is permitted.
+marked as resolved before a commit is permitted.
 The codes used to show the status of files are::
 U = unresolved
 R = resolved
 util.rename(a + ".resolve", a + ".orig")
 def revert(ui, repo, *pats, **opts):
 """restore individual files or directories to an earlier state
-(Use update -r to check out earlier revisions, revert does not change the
+(Use update -r to check out earlier revisions, revert does not
-working directory parents.)
+change the working directory parents.)
-With no revision specified, revert the named files or directories to the
+With no revision specified, revert the named files or directories
-contents they had in the parent of the working directory. This restores
+to the contents they had in the parent of the working directory.
-the contents of the affected files to an unmodified state and unschedules
+This restores the contents of the affected files to an unmodified
-adds, removes, copies, and renames. If the working directory has two
+state and unschedules adds, removes, copies, and renames. If the
-parents, you must explicitly specify the revision to revert to.
+working directory has two parents, you must explicitly specify the
+revision to revert to.
-Using the -r/--rev option, revert the given files or directories to their
-contents as of a specific revision. This can be helpful to "roll back"
+Using the -r/--rev option, revert the given files or directories
-some or all of an earlier change. See 'hg help dates' for a list of
+to their contents as of a specific revision. This can be helpful
-formats valid for -d/--date.
+to "roll back" some or all of an earlier change. See 'hg help
+dates' for a list of formats valid for -d/--date.
-Revert modifies the working directory. It does not commit any changes, or
-change the parent of the working directory. If you revert to a revision
+Revert modifies the working directory. It does not commit any
-other than the parent of the working directory, the reverted files will
+changes, or change the parent of the working directory. If you
-thus appear modified afterwards.
+revert to a revision other than the parent of the working
+directory, the reverted files will thus appear modified
-If a file has been deleted, it is restored. If the executable mode of a
+afterwards.
-file was changed, it is reset.
+If a file has been deleted, it is restored. If the executable mode
-If names are given, all files matching the names are reverted. If no
+of a file was changed, it is reset.
-arguments are given, no files are reverted.
+If names are given, all files matching the names are reverted.
-Modified files are saved with a .orig suffix before reverting. To disable
+If no arguments are given, no files are reverted.
-these backups, use --no-backup.
+Modified files are saved with a .orig suffix before reverting.
+To disable these backups, use --no-backup.
 """
 if opts["date"]:
 if opts["rev"]:
 raise util.Abort(_("you can't specify a revision and a date"))
 def rollback(ui, repo):
 """roll back the last transaction
 This command should be used with care. There is only one level of
-rollback, and there is no way to undo a rollback. It will also restore the
+rollback, and there is no way to undo a rollback. It will also
-dirstate at the time of the last transaction, losing any dirstate changes
+restore the dirstate at the time of the last transaction, losing
-since that time. This command does not alter the working directory.
+any dirstate changes since that time. This command does not alter
+the working directory.
-Transactions are used to encapsulate the effects of all commands that
-create new changesets or propagate existing changesets into a repository.
+Transactions are used to encapsulate the effects of all commands
-For example, the following commands are transactional, and their effects
+that create new changesets or propagate existing changesets into a
-can be rolled back::
+repository. For example, the following commands are transactional,
+and their effects can be rolled back::
 commit
 import
 pull
 push (with this repository as destination)
 unbundle
-This command is not intended for use on public repositories. Once changes
+This command is not intended for use on public repositories. Once
-are visible for pull by other users, rolling a transaction back locally is
+changes are visible for pull by other users, rolling a transaction
-ineffective (someone else may already have pulled the changes).
+back locally is ineffective (someone else may already have pulled
-Furthermore, a race is possible with readers of the repository; for
+the changes). Furthermore, a race is possible with readers of the
-example an in-progress pull from the repository may fail if a rollback is
+repository; for example an in-progress pull from the repository
-performed.
+may fail if a rollback is performed.
 """
 repo.rollback()
 def root(ui, repo):
 """print the root (top) of the current working directory
 def serve(ui, repo, **opts):
 """export the repository via HTTP
 Start a local HTTP repository browser and pull server.
-By default, the server logs accesses to stdout and errors to stderr. Use
+By default, the server logs accesses to stdout and errors to
-the -A/--accesslog and -E/--errorlog options to log to files.
+stderr. Use the -A/--accesslog and -E/--errorlog options to log to
+files.
 """
 if opts["stdio"]:
 if repo is None:
 raise error.RepoError(_("There is no Mercurial repository here"
 cmdutil.service(opts, initfn=service.init, runfn=service.run)
 def status(ui, repo, *pats, **opts):
 """show changed files in the working directory
-Show status of files in the repository. If names are given, only files
+Show status of files in the repository. If names are given, only
-that match are shown. Files that are clean or ignored or the source of a
+files that match are shown. Files that are clean or ignored or
-copy/move operation, are not listed unless -c/--clean, -i/--ignored,
+the source of a copy/move operation, are not listed unless
--C/--copies or -A/--all are given. Unless options described with "show
+-c/--clean, -i/--ignored, -C/--copies or -A/--all are given.
-only ..." are given, the options -mardu are used.
+Unless options described with "show only ..." are given, the
+options -mardu are used.
-Option -q/--quiet hides untracked (unknown and ignored) files unless
-explicitly requested with -u/--unknown or -i/--ignored.
+Option -q/--quiet hides untracked (unknown and ignored) files
+unless explicitly requested with -u/--unknown or -i/--ignored.
-NOTE: status may appear to disagree with diff if permissions have changed
-or a merge has occurred. The standard diff format does not report
+NOTE: status may appear to disagree with diff if permissions have
-permission changes and diff only reports changes relative to one merge
+changed or a merge has occurred. The standard diff format does not
-parent.
+report permission changes and diff only reports changes relative
+to one merge parent.
-If one revision is given, it is used as the base revision. If two
-revisions are given, the differences between them are shown.
+If one revision is given, it is used as the base revision.
+If two revisions are given, the differences between them are
+shown.
 The codes used to show the status of files are::
 M = modified
 A = added
 def tag(ui, repo, name1, *names, **opts):
 """add one or more tags for the current or given revision
 Name a particular revision using <name>.
-Tags are used to name particular revisions of the repository and are very
+Tags are used to name particular revisions of the repository and are
-useful to compare different revisions, to go back to significant earlier
+very useful to compare different revisions, to go back to significant
-versions or to mark branch points as releases, etc.
+earlier versions or to mark branch points as releases, etc.
-If no revision is given, the parent of the working directory is used, or
+If no revision is given, the parent of the working directory is
-tip if no revision is checked out.
+used, or tip if no revision is checked out.
-To facilitate version control, distribution, and merging of tags, they are
+To facilitate version control, distribution, and merging of tags,
-stored as a file named ".hgtags" which is managed similarly to other
+they are stored as a file named ".hgtags" which is managed
-project files and can be hand-edited if necessary. The file
+similarly to other project files and can be hand-edited if
-'.hg/localtags' is used for local tags (not shared among repositories).
+necessary. The file '.hg/localtags' is used for local tags (not
+shared among repositories).
 See 'hg help dates' for a list of formats valid for -d/--date.
 """
 rev_ = "."
 repo.tag(names, r, message, opts.get('local'), opts.get('user'), date)
 def tags(ui, repo):
 """list repository tags
-This lists both regular and local tags. When the -v/--verbose switch is
+This lists both regular and local tags. When the -v/--verbose
-used, a third column "local" is printed for local tags.
+switch is used, a third column "local" is printed for local tags.
 """
 hexfunc = ui.debugflag and hex or short
 tagtype = ""
 ui.write("%s%s %s%s\n" % (t, spaces, r, tagtype))
 def tip(ui, repo, **opts):
 """show the tip revision
-The tip revision (usually just called the tip) is the changeset most
+The tip revision (usually just called the tip) is the changeset
-recently added to the repository (and therefore the most recently changed
+most recently added to the repository (and therefore the most
-head).
+recently changed head).
-If you have just made a commit, that commit will be the tip. If you have
+If you have just made a commit, that commit will be the tip. If
-just pulled changes from another repository, the tip of that repository
+you have just pulled changes from another repository, the tip of
-becomes the current tip. The "tip" tag is special and cannot be renamed or
+that repository becomes the current tip. The "tip" tag is special
-assigned to a different changeset.
+and cannot be renamed or assigned to a different changeset.
 """
 cmdutil.show_changeset(ui, repo, opts).show(repo[len(repo) - 1])
 def unbundle(ui, repo, fname1, *fnames, **opts):
 """apply one or more changegroup files
-Apply one or more compressed changegroup files generated by the bundle
+Apply one or more compressed changegroup files generated by the
-command.
+bundle command.
 """
 fnames = (fname1,) + fnames
 lock = repo.lock()
 try:
 return postincoming(ui, repo, modheads, opts.get('update'), None)
 def update(ui, repo, node=None, rev=None, clean=False, date=None, check=False):
 """update working directory
-Update the repository's working directory to the specified revision, or
+Update the repository's working directory to the specified
-the tip of the current branch if none is specified. Use null as the
+revision, or the tip of the current branch if none is specified.
-revision to remove the working copy (like 'hg clone -U').
+Use null as the revision to remove the working copy (like 'hg
+clone -U').
-When the working directory contains no uncommitted changes, it will be
-replaced by the state of the requested revision from the repository. When
+When the working directory contains no uncommitted changes, it
-the requested revision is on a different branch, the working directory
+will be replaced by the state of the requested revision from the
-will additionally be switched to that branch.
+repository. When the requested revision is on a different branch,
+the working directory will additionally be switched to that
-When there are uncommitted changes, use option -C/--clean to discard them,
+branch.
-forcibly replacing the state of the working directory with the requested
-revision. Alternately, use -c/--check to abort.
+When there are uncommitted changes, use option -C/--clean to
+discard them, forcibly replacing the state of the working
-When there are uncommitted changes and option -C/--clean is not used, and
+directory with the requested revision. Alternately, use -c/--check
-the parent revision and requested revision are on the same branch, and one
+to abort.
-of them is an ancestor of the other, then the new working directory will
-contain the requested revision merged with the uncommitted changes.
+When there are uncommitted changes and option -C/--clean is not
-Otherwise, the update will fail with a suggestion to use 'merge' or
+used, and the parent revision and requested revision are on the
-'update -C' instead.
+same branch, and one of them is an ancestor of the other, then the
+new working directory will contain the requested revision merged
-If you want to update just one file to an older revision, use revert.
+with the uncommitted changes. Otherwise, the update will fail with
+a suggestion to use 'merge' or 'update -C' instead.
+If you want to update just one file to an older revision, use
+revert.
 See 'hg help dates' for a list of formats valid for -d/--date.
 """
 if rev and node:
 raise util.Abort(_("please specify just one revision"))
 def verify(ui, repo):
 """verify the integrity of the repository
 Verify the integrity of the current repository.
-This will perform an extensive check of the repository's integrity,
+This will perform an extensive check of the repository's
-validating the hashes and checksums of each entry in the changelog,
+integrity, validating the hashes and checksums of each entry in
-manifest, and tracked files, as well as the integrity of their crosslinks
+the changelog, manifest, and tracked files, as well as the
-and indices.
+integrity of their crosslinks and indices.
 """
 return hg.verify(repo)
 def version_(ui):
 """output version and copyright information"""

changeset 9249	16f4cfc69e4f
parent 9219	3f650f6aa130
child 9280	b694531a5aa7