Kiln » TortoiseHg » TortoiseHg
Clone URL:  
Pushed to one repository · View In Graph Contained in 0.8.1, 0.8.2, and 0.8.3

doc: add the module directive in each chapter

so the modindex.html will be generated

Changeset 4fc34be72bc8…

Parent 7fd5422da0d0…

by Giampaolo Fadel

Changes to 10 files · Browse files at 4fc34be72bc8 Showing diff from parent 7fd5422da0d0 Diff from another changeset...

Change 1 of 1 Show Entire File doc/​source/​changelog.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 TortoiseHg Changelog Viewer  ===========================   +.. module:: changelog.dialog + :synopsis: Dialog used to view log +  .. figure:: figures/log.png   :alt: Changelog  
Change 1 of 1 Show Entire File doc/​source/​commit.txt Stacked
 
2
3
4
 
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
11
@@ -2,6 +2,10 @@
 TortoiseHg Commit Tool  ======================   +.. module:: commit.dialog + :synopsis: Dialog used to perform commit + +  This page describes the 0.8 version of commit    **The win32text extension can cause trouble with hunk selection. This
Change 1 of 1 Show Entire File doc/​source/​common.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 Common Features  ===============   +.. module:: common.dialog + :synopsis: Common features to all the dialog +  These features are commonly available in many TortoiseHg tools, so we  document them here just once.  
Change 1 of 1 Show Entire File doc/​source/​datamine.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 TortoiseHg Datamine  ===================   +.. module:: datamine.dialog + :synopsis: Dialog used to search in the history +  This page describes the 0.7 version of datamine    The datamine application is used to inspect the revision history of your
Change 1 of 1 Show Entire File doc/​source/​explorer.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 Windows Explorer Integration  ============================   +.. module:: explorer + :synopsis: Windows explorer integration +  Overlay Icons  -------------  TortoiseHg provides visual representation of the file status via overlay
Change 1 of 1 Show Entire File doc/​source/​recovery.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 TortoiseHg Recovery  ===================   +.. module:: recovery.dialog + :synopsis: Dialog used to perform recovery operations +  This page describes the 0.7 version of recovery, though very little was  changed in 0.8  
Change 1 of 1 Show Entire File doc/​source/​serve.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 TortoiseHg Serve  ================   +.. module:: serve.dialog + :synopsis: Dialog used to start/stop the web server +  The serve tool is a wrapper for Mercurial's built-in web server. Once  launched, any computer can attach to the http port and browse your  repository(ies) or perform clone, pull, or even push operations (if you
Change 1 of 1 Show Entire File doc/​source/​settings.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 TortoiseHg Settings  ===================   +.. module:: settings.dialog + :synopsis: Dialog used to set preferences +  This page describes the 0.7 version of settings    The Settings dialog is used to configure both TortoiseHg and the
Change 1 of 1 Show Entire File doc/​source/​shelve.txt Stacked
 
2
3
4
 
 
 
5
6
7
 
2
3
4
5
6
7
8
9
10
@@ -2,6 +2,9 @@
 TortoiseHg Shelve Tool  ======================   +.. module:: commit.dialog + :synopsis: Dialog used to perform shelve/unshelve operations +  **The win32text extension can cause trouble with hunk selection. This  has been resolved in Mercurial 1.3 and TortoiseHg 0.8, but requires  proper configuration. See issue #82.**
Change 1 of 1 Show Changes Only doc/​source/​synchronize.txt Stacked
1
2
3
4
 
 
 
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
 ======================  TortoiseHg Synchronize  ======================   +.. module:: synchronize.dialog + :synopsis: Dialog used to perform synchronization operations +  This page describes the 0.7 version of synchronize    The synchronize tool is used to transmit changesets between repositories  and to email recipients.      .. figure:: figures/synchronize.png   :alt: Synchronize dialog     Synchronize dialog    *Incoming*   show changesets that would be pulled from target repository  *Pull*   pull incoming changesets from target repository [1]  *Outgoing*   show changesets that would be pushed to target repository  *Push*   push outgoing changesets to target repository  *Email*   send outgoing changesets (to target repository) as email  *Stop*   stop current operation  *Configure*   Configure repository paths (aliases)    1) The *Pull* toolbutton has a drop-down menu with extra options that  are only applicable to pull operations: *Update after Pull*, and *Use  fetch*. See the fetch extension documentation for it's behavior.    The *Repo:* button will open a directory finder to locate another  repository on your local computer to synchronize with. Similarly, the  *Bundle* button will open a file finder to locate a Mercurial bundle  (``.hg``) file to pull changes 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, and with the most 10 recent  paths used with any repository. There will be a dashed separator between  the configured paths and the history.    The *use proxy* button is a quick way to disable your proxy  configuration for just a few operations. The button is only sensitive  when you have an http proxy 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 FAQ1_ for help if  you have trouble connecting to ssh servers.    .. _FAQ1: http://bitbucket.org/tortoisehg/stable/wiki/FAQ#tortoisehg-faq    Under the *Advanced Options* fold-up panel are a number of configurables  that are valid for most push/pull operations.    *Specify target revision for transmission*   to avoid sending all revisions  *Force pull or push*   override warnings about multiple heads or unrelated repositories  *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 Pull  ----------    After changesets are pulled into your repository, two buttons may appear  at the bottom of the dialog:    *View pulled changesets*   Open the changelog viewer and inspect pulled changesets  *Update to tip*   Update your working directory to the new tip    Either button may be hidden if it is not applicable.    Email  -----    The email dialog can be launched from two TortoiseHg tools.    1) The changelog tool, in which case the user intends to email a single  revision    2) The synchronize tool, in which case the user intends to email all  outgoing changes to the current target repository (it's good practice to  check the outgoing changes before launching the email dialog).    .. figure:: figures//email.png   :alt: Email dialog     Email dialog    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.    Please consult the Mercurial documentation for the differences between  plain patches, HG patches, Git patches, and bundles.