[Bug 5744] New: help text for hg bundle doesn't explain what [DEST] is for
mercurial-bugs at mercurial-scm.org
mercurial-bugs at mercurial-scm.org
Fri Nov 17 11:54:50 UTC 2017
https://bz.mercurial-scm.org/show_bug.cgi?id=5744
Bug ID: 5744
Summary: help text for hg bundle doesn't explain what [DEST] is
for
Product: Mercurial
Version: 4.3.1
Hardware: PC
OS: Windows
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: Mercurial
Assignee: bugzilla at mercurial-scm.org
Reporter: david.a.hollman at carrier.utc.com
CC: mercurial-devel at mercurial-scm.org
The help text for the hg bundle command indicates there is an optional argument
[DEST] which may be used but it does not explain what the argument is for.
The --verbose option doesn't add this information either.
Sample output placed below.
----
λ hg --version
Mercurial Distributed SCM (version 4.3.1)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2017 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
λ hg bundle --help
hg bundle [-f] [-t BUNDLESPEC] [-a] [-r REV]... [--base REV]... FILE [DEST]
create a bundle file
Generate a bundle file containing data to be added to a repository.
To create a bundle containing all changesets, use -a/--all (or --base
null). Otherwise, hg assumes the destination will have all the nodes you
specify with --base parameters. Otherwise, hg will assume the repository
has all the nodes in destination, or default-push/default if no
destination is specified.
You can change bundle format with the -t/--type option. See 'hg help
bundlespec' for documentation on this format. By default, the most
appropriate format is used and compression defaults to bzip2.
The bundle file can then be transferred using conventional means and
applied to another repository with the unbundle or pull 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.
Returns 0 on success, 1 if no changes found.
options ([+] can be repeated):
-f --force run even when the destination is unrelated
-r --rev REV [+] a changeset intended to be added to the destination
-b --branch BRANCH [+] a specific branch you would like to bundle
--base REV [+] a base changeset assumed to be available at the
destination
-a --all bundle all changesets in the repository
-t --type TYPE bundle compression type to use (default: bzip2)
-e --ssh CMD specify ssh command to use
--remotecmd CMD specify hg command to run on the remote side
--insecure do not verify server certificate (ignoring web.cacerts
config)
(some details hidden, use --verbose to show complete help)
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list