|
Size: 1497
Comment:
|
Size: 2212
Comment: Update documentation.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| TortoiseHg GUI Extension: [[http://bitbucket.org/MrWerewolf/tortoisehg-rupdate/downloads|binaries]] | [[http://bitbucket.org/MrWerewolf/tortoisehg-rupdate|source]] | ''TortoiseHg will support this extension in it's next feature release.'' |
| Line 14: | Line 14: |
| Remote Update is an extension for Mercurial (Hg) that adds the ability to update a remote repository's working directory to a specified revision if the remote repository is hosted via ssh. | Remote Update is an extension for Mercurial (Hg) that adds the ability to update a remote repository's working directory to a specified revision if the remote repository is hosted via ssh. |
| Line 16: | Line 18: |
| This can help simplify the process for maintaining a website that is a Mercurial repository with it's own working directory. | This can help simplify the process for maintaining a website that is a Mercurial repository with it's own working directory. |
| Line 19: | Line 22: |
| Configure your .hgrc to enable the extension by adding following lines: | Configure your .hgrc or mercurial.ini to enable the extension by adding the following lines: |
| Line 28: | Line 33: |
| When you run rupdate it will first perform a push to the remote repository to ensure that the revision exists at the remote location. Then it will run the "hg update" command at the remote location. If you have not setup passwordless authentication you will be asked for a password more than once. | {{{ hg rupdate [OPTIONS] [-d DEST] REV }}} To update the ''default'' remote repository to revision e9e4e6afc30a: |
| Line 33: | Line 42: |
| $ hg rupdate 11 searching for changes no changes found Updating the remote repository to revision: 11 0 files updated, 0 files merged, 0 files removed, 0 files unresolved Remote repository updated |
hg rupdate e9e4e6afc30a |
| Line 40: | Line 44: |
==== Options ==== `-p`, `--push` Performs a push to the remote repository before updating it. If you have not setup passwordless authentication you will be asked for a password more than once. `-f`, `--force` This will perform the equivalent of `hg push --force` when pushing. This only has an effect if the `--push` option is used. `--new-branch` This will perform the equivalent of `hg push --new-branch`, allowing new branchs to be pushed. This only has an effect if the `--push` option is used. `-C`, `--clean` Discards uncommited remote changes (no backup). This is equivalent to running `hg update --clean` on the remote location. `-d` *DEST*, `--dest` *DEST* Specifies the remote location to update. This can be an alias or a full `ssh://` path. `-r` *REV*, `--rev` *REV*, *REV* Secifies the revision to update to on the remote location. You can use the same format that you would with `hg update REV`. This means *REV* can be a branch name or a tag name. '''Note:''' ''It is dangerous to use the revision number. To update a specific revision, use unique identifier (hash code).'' |
Remote Update
This extension is not distributed with Mercurial.
Author: Ryan Seto
Mercurial Extension: http://bitbucket.org/MrWerewolf/rupdate
TortoiseHg will support this extension in it's next feature release.
Overview
Remote Update is an extension for Mercurial (Hg) that adds the ability to update a remote repository's working directory to a specified revision if the remote repository is hosted via ssh.
This can help simplify the process for maintaining a website that is a Mercurial repository with it's own working directory.
Configuration
Configure your .hgrc or mercurial.ini to enable the extension by adding the following lines:
[extensions] rupdate = /path/to/rupdate
Usage
hg rupdate [OPTIONS] [-d DEST] REV
To update the default remote repository to revision e9e4e6afc30a:
To update the default remote repository to revision 11.
hg rupdate e9e4e6afc30a
Options
-p, --push
- Performs a push to the remote repository before updating it. If you have not setup passwordless authentication you will be asked for a password more than once.
-f, --force
This will perform the equivalent of hg push --force when pushing. This only has an effect if the --push option is used.
--new-branch
This will perform the equivalent of hg push --new-branch, allowing new branchs to be pushed. This only has an effect if the --push option is used.
-C, --clean
Discards uncommited remote changes (no backup). This is equivalent to running hg update --clean on the remote location.
-d *DEST*, --dest *DEST*
Specifies the remote location to update. This can be an alias or a full ssh:// path.
-r *REV*, --rev *REV*, *REV*
Secifies the revision to update to on the remote location. You can use the same format that you would with hg update REV. This means *REV* can be a branch name or a tag name.
Note: It is dangerous to use the revision number. To update a specific revision, use unique identifier (hash code).