Show More
@@ -426,7 +426,7 b' def _disabledhelp(path):' | |||
|
426 | 426 | file.close() |
|
427 | 427 | |
|
428 | 428 | if doc: # extracting localized synopsis |
|
429 |
return gettext(doc) |
|
|
429 | return gettext(doc) | |
|
430 | 430 | else: |
|
431 | 431 | return _('(no help text available)') |
|
432 | 432 | |
@@ -448,7 +448,7 b' def disabled():' | |||
|
448 | 448 | for name, path in paths.iteritems(): |
|
449 | 449 | doc = _disabledhelp(path) |
|
450 | 450 | if doc: |
|
451 | exts[name] = doc | |
|
451 | exts[name] = doc.splitlines()[0] | |
|
452 | 452 | |
|
453 | 453 | return exts |
|
454 | 454 |
@@ -1045,6 +1045,61 b' Disabled extensions:' | |||
|
1045 | 1045 | $ hg help patchbomb |
|
1046 | 1046 | patchbomb extension - command to send changesets as (a series of) patch emails |
|
1047 | 1047 | |
|
1048 | The series is started off with a "[PATCH 0 of N]" introduction, which | |
|
1049 | describes the series as a whole. | |
|
1050 | ||
|
1051 | Each patch email has a Subject line of "[PATCH M of N] ...", using the first | |
|
1052 | line of the changeset description as the subject text. The message contains | |
|
1053 | two or three body parts: | |
|
1054 | ||
|
1055 | - The changeset description. | |
|
1056 | - [Optional] The result of running diffstat on the patch. | |
|
1057 | - The patch itself, as generated by 'hg export'. | |
|
1058 | ||
|
1059 | Each message refers to the first in the series using the In-Reply-To and | |
|
1060 | References headers, so they will show up as a sequence in threaded mail and | |
|
1061 | news readers, and in mail archives. | |
|
1062 | ||
|
1063 | To configure other defaults, add a section like this to your configuration | |
|
1064 | file: | |
|
1065 | ||
|
1066 | [email] | |
|
1067 | from = My Name <my@email> | |
|
1068 | to = recipient1, recipient2, ... | |
|
1069 | cc = cc1, cc2, ... | |
|
1070 | bcc = bcc1, bcc2, ... | |
|
1071 | reply-to = address1, address2, ... | |
|
1072 | ||
|
1073 | Use "[patchbomb]" as configuration section name if you need to override global | |
|
1074 | "[email]" address settings. | |
|
1075 | ||
|
1076 | Then you can use the 'hg email' command to mail a series of changesets as a | |
|
1077 | patchbomb. | |
|
1078 | ||
|
1079 | You can also either configure the method option in the email section to be a | |
|
1080 | sendmail compatible mailer or fill out the [smtp] section so that the | |
|
1081 | patchbomb extension can automatically send patchbombs directly from the | |
|
1082 | commandline. See the [email] and [smtp] sections in hgrc(5) for details. | |
|
1083 | ||
|
1084 | By default, 'hg email' will prompt for a "To" or "CC" header if you do not | |
|
1085 | supply one via configuration or the command line. You can override this to | |
|
1086 | never prompt by configuring an empty value: | |
|
1087 | ||
|
1088 | [email] | |
|
1089 | cc = | |
|
1090 | ||
|
1091 | You can control the default inclusion of an introduction message with the | |
|
1092 | "patchbomb.intro" configuration option. The configuration is always | |
|
1093 | overwritten by command line flags like --intro and --desc: | |
|
1094 | ||
|
1095 | [patchbomb] | |
|
1096 | intro=auto # include introduction message if more than 1 patch (default) | |
|
1097 | intro=never # never include an introduction message | |
|
1098 | intro=always # always include an introduction message | |
|
1099 | ||
|
1100 | You can set patchbomb to always ask for confirmation by setting | |
|
1101 | "patchbomb.confirm" to true. | |
|
1102 | ||
|
1048 | 1103 | (use 'hg help extensions' for information on enabling extensions) |
|
1049 | 1104 | |
|
1050 | 1105 |
@@ -9,6 +9,9 b' help record (no record)' | |||
|
9 | 9 | record extension - commands to interactively select changes for |
|
10 | 10 | commit/qrefresh (DEPRECATED) |
|
11 | 11 | |
|
12 | The feature provided by this extension has been moved into core Mercurial as | |
|
13 | 'hg commit --interactive'. | |
|
14 | ||
|
12 | 15 | (use 'hg help extensions' for information on enabling extensions) |
|
13 | 16 | |
|
14 | 17 | help qrecord (no record) |
General Comments 0
You need to be logged in to leave comments.
Login now