Kiln » TortoiseHg » TortoiseHg
Clone URL:  
Pushed to one repository · View In Graph Contained in 2.0, 2.0.1, and 2.0.2

stable doc: use file name typographical convention in extensions.txt

Changeset e037f2789648…

Parent 611866546663…

by André Sintzoff

Changes to one file · Browse files at e037f2789648 Showing diff from parent 611866546663 Diff from another changeset...

Change 1 of 5 Show Entire File doc/​source/​extensions.txt Stacked
 
87
88
89
90
 
91
92
93
 
108
109
110
111
 
 
112
113
114
 
123
124
125
126
127
 
 
128
129
130
 
140
141
142
143
144
 
 
145
146
147
 
151
152
153
154
155
156
 
 
 
157
158
159
 
87
88
89
 
90
91
92
93
 
108
109
110
 
111
112
113
114
115
 
124
125
126
 
 
127
128
129
130
131
 
141
142
143
 
 
144
145
146
147
148
 
152
153
154
 
 
 
155
156
157
158
159
160
@@ -87,7 +87,7 @@
 to/from given remote repository (just like it is done by default), but  saves the password (keyed by the combination of username and remote  repository url) in the password database. On the next run it checks for -the username in .hg/hgrc, then for suitable password in the password +the username in :file:`.hg/hgrc`, then for suitable password in the password  database, and uses those credentials if found.    Similarly, while sending emails via SMTP server which requires @@ -108,7 +108,8 @@
   The most appropriate password backend should usually be picked automatically,  without configuration. Still, if necessary, it can be configured using -~/keyringrc.cfg file (keyringrc.cfg in the home directory of the current user). +:file:`~/keyringrc.cfg` file (:file:`keyringrc.cfg` in the home directory of +the current user).  Refer to `keyring docs <http://pypi.python.org/pypi/keyring>`_  for more details.   @@ -123,8 +124,8 @@
   **Repository configuration (HTTP)**   -Edit repository-local .hg/hgrc and save there the remote repository path and -the username, but do not save the password. For example:: +Edit repository-local :file:`.hg/hgrc` and save there the remote repository +path and the username, but do not save the password. For example::     [paths]   myremote = https://my.server.com/hgrepo/someproject @@ -140,8 +141,8 @@
  bitbucket = https://User@bitbucket.org/User/project_name/    .. note:: - If both username and password are given in .hg/hgrc, extension will - use them without using the password database. If username is not + If both username and password are given in :file:`.hg/hgrc`, extension + will use them without using the password database. If username is not   given, extension will prompt for credentials every time, also   without saving the password. So, in both cases, it is effectively   reverting to the default behaviour. @@ -151,9 +152,9 @@
   **Repository configuration (SMTP)**   -Edit either repository-local .hg/hgrc, or ~/.hgrc (the latter is usually -preferable) and set there all standard email and smtp properties, including -smtp username, but without smtp password. For example:: +Edit either repository-local :file:`.hg/hgrc`, or :file:`~/.hgrc` (the latter +is usually preferable) and set there all standard email and smtp properties, +including smtp username, but without smtp password. For example::     [email]   method = smtp