Synchronize dialog
Note
The synchronize tool has been deprecated in the 0.9 release, and may be removed in a future release. We suggest you use the changelog tool for performing synchronization duties.
The synchronize tool is used to transmit changesets between repositories or to email recipients.
- Incoming
- show changesets that would be pulled from target repository, the changes in the target repository that are not in local repository
- Pull
- pull incoming changesets from target repository
- Outgoing
- show changesets that would be pushed to target repository, the changes in the local repository that are not in target repository
- Push
- push outgoing changesets to target repository, make the local tip the new tip in the target repository
- send outgoing changesets (to target repository) as email
- Shelve
- launch the shelve tool to allow working changes to be temporarily moved into the shelf, since some operations require the working directory to be clean.
- Stop
- stop current operation
- Configure
- configure repository paths (aliases)
Below the toolbar are two buttons and a text entry:
- Repo:
- browse for a local repository to synchronize with
- Bundle:
- browse for a local bundle file to pull from
The text entry/combo box is where you enter or select paths of target repositories. The synchronize tool will seed the drop-down list with path aliases configured for this repository.
The Post Pull Operation frame contains radio buttons for selecting the operation which is performed after a pull. This behavior is configurable via the Configure button. You can select a default behavior for your user account and override that selection on a per-repository basis.
- Nothing
- No operations are performed after a pull. You will be allowed to view the pulled changesets in the log viewer, and you will have the option to update to the new tip if applicable.
- Update
- Automatically update to the new branch tip if, and only if, new revisions were pulled into the local repository. This could trigger a merge if the pulled changes conflict with local uncommitted changes.
- Fetch
- Equivalent to hg fetch. See the fetch extension documentation for it’s behavior. This feature is only available if the fetch extension has been enabled by the user.
- Rebase
- Equivalent to pull –rebase. See the rebase extension documentation for it’s behavior. This feature is only available if the rebase extension has been enabled by the user.
The use proxy button is a quick way to disable your proxy configuration for individual operations. The button is only sensitive when an http proxy is configured.
All operations which require authentication will pop up dialog boxes to get the required information from the user. TortoiseHg uses the TortoisePlink tool (borrowed from the TortoiseSVN distribution) to handle ssh: connections and authentication. See the FAQ for help if you have trouble connecting to ssh servers.
Under the Advanced Options fold-up panel are a number of configurables that are valid for most push/pull operations.
- Force pull or push
- override warnings about multiple heads or unrelated repositories
- Target Revision
- to avoid sending all revisions
- Remote Command
- provides -e argument
- Show patches
- show diffs in incoming and outging changes
- Show Newest First
- reverse order that changesets are listed
- Show No Merges
- filter out merge changesets from output (does not affect push/pull)
After changesets are pulled into your repository, a buttons may appear at the bottom of the dialog:
- Update to branch tip
- Update your working directory to the new tip of the current branch
The button will be hidden when it is not applicable.
Email dialog
The email dialog can be launched from two TortoiseHg tools.
The Send button is obvious, and the Configure dialog predictably opens the TortoiseHg Settings dialog to the email tab where you can configure your SMTP settings and set default To: and From: addresses.
In-Reply-To: is used to make your patches properly threaded in mailing lists.
Please consult the Mercurial documentation for the differences between plain patches, HG patches, Git patches, and bundles.
The synchronize tool can be started from command line
hgtk synch
aliases: pull, push, incoming, outgoing, email
repository synchronization tool
use "hgtk -v help synch" to show global options
The syntax is simple, no options or parameters are needed, except the global options. If the synchronize tool is started via push, outgoing, or email command aliases, it will automatically select the default-push URL if. For all other aliases the tool selects the default URL. If the selected URL is not found, it will use the first path it finds.