517
Comment: fix configuration
|
← Revision 8 as of 2013-02-22 11:11:53 ⇥
886
Add warning that fetch is in the unloved feature list.
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
/!\ This is an [[UnlovedFeatures|unloved feature]]. |
|
Line 4: | Line 7: |
''Author: Vadim Gelfer'' |
|
Line 5: | Line 10: |
This extension pulls changes from a remote repository and merges new changes if needed, and finally updates the working directory. | This extension is a convenience wrapper. In the simplest case, {{{hg fetch}}} acts like {{{hg pull -u}}} -- it pulls changes from a remote repository into a local one and updates the working directory. (This is like the "update" command as found in Subversion or CVS.) If the pulled changes require merging, the fetch extension attempts an {{{hg merge}}} followed by an {{{hg commit}}}. |
Line 8: | Line 15: |
Configure your .hgrc to enable the extension by adding following lines: | To enable the extension, add the following lines to your .hgrc: |
Line 22: | Line 29: |
---- CategoryBundledExtension |
Fetch extension
This is an unloved feature.
This extension is currently being distributed along with Mercurial.
Author: Vadim Gelfer
Overview
This extension is a convenience wrapper. In the simplest case, hg fetch acts like hg pull -u -- it pulls changes from a remote repository into a local one and updates the working directory. (This is like the "update" command as found in Subversion or CVS.)
If the pulled changes require merging, the fetch extension attempts an hg merge followed by an hg commit.
Configuration
To enable the extension, add the following lines to your .hgrc:
[extensions] hgext.fetch=
Usage
hg fetch [SOURCE]
Where SOURCE is a path or URL.
Use hg help fetch for additional options.