Differences between revisions 8 and 9
Revision 8 as of 2008-01-13 15:55:53
Size: 190
Editor: abuehl
Comment: lowercase links
Revision 9 as of 2008-04-19 23:43:52
Size: 1669
Editor: abuehl
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
''hg push'' `hg push [-f] [-r REV]... [-e CMD] [--remotecmd CMD] [DEST]`
Line 7: Line 7:
See also: ["Pull"], ["CommunicatingChanges"] === Help text ===

{{{
hg push [-f] [-r REV]... [-e CMD] [--remotecmd CMD] [DEST]

push changes to the specified destination

    Push changes from the local repository to the given destination.

    This is the symmetrical operation for pull. It helps to move
    changes from the current repository to a different one. If the
    destination is 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
    the client has forgotten to sync and merge before pushing.

    Valid URLs are of the form:

      local/filesystem/path (or file://local/filesystem/path)
      ssh://[user@]host[:port]/[path]
      http://[user@]host[:port]/[path]
      https://[user@]host[:port]/[path]

    An optional identifier after # indicates a particular branch, tag,
    or changeset to push.

    Look at the help text for the pull command for important details
    about ssh:// URLs.

    Pushing to http:// and https:// URLs is only possible, if this
    feature is explicitly enabled on the remote Mercurial server.

options:

 -f --force force push
 -r --rev a specific revision up to which you would like to push
 -e --ssh specify ssh command to use
    --remotecmd specify hg command to run on the remote side
}}}

See also: [:Pull], [:CommunicatingChanges]

Push

hg push [-f] [-r REV]... [-e CMD] [--remotecmd CMD] [DEST]

A push propagates changes from a local [:Repository:repository] to a remote one.

Help text

hg push [-f] [-r REV]... [-e CMD] [--remotecmd CMD] [DEST]

push changes to the specified destination

    Push changes from the local repository to the given destination.

    This is the symmetrical operation for pull. It helps to move
    changes from the current repository to a different one. If the
    destination is 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
    the client has forgotten to sync and merge before pushing.

    Valid URLs are of the form:

      local/filesystem/path (or file://local/filesystem/path)
      ssh://[user@]host[:port]/[path]
      http://[user@]host[:port]/[path]
      https://[user@]host[:port]/[path]

    An optional identifier after # indicates a particular branch, tag,
    or changeset to push.

    Look at the help text for the pull command for important details
    about ssh:// URLs.

    Pushing to http:// and https:// URLs is only possible, if this
    feature is explicitly enabled on the remote Mercurial server.

options:

 -f --force      force push
 -r --rev        a specific revision up to which you would like to push
 -e --ssh        specify ssh command to use
    --remotecmd  specify hg command to run on the remote side

See also: [:Pull], [:CommunicatingChanges]


CategoryCommand