##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

add test for patchbomb extension.
Bryan O'Sullivan -
r4420:b0656b33 default
parent child Browse files
Show More
Show file before | Show file after | Hide comments
@@ -0,0 +1,17 b''
1 #!/bin/sh
2
3 echo "[extensions]" >> $HGRCPATH
4 echo "patchbomb=" >> $HGRCPATH
5
6 hg init
7 echo a > a
8 hg commit -Ama -d '1 0'
9
10 hg email --date '1970-1-1 0:1' -n -f quux -t foo -c bar tip | \
11 sed -e 's/\(Message-Id:.*@\).*/\1/'
12
13 echo b > b
14 hg commit -Amb -d '2 0'
15
16 hg email --date '1970-1-1 0:2' -n -f quux -t foo -c bar -s test 0:tip | \
17 sed -e 's/\(Message-Id:.*@\|In-Reply-To:.*@\).*/\1/'
Show file before | Show file after | Hide comments
@@ -0,0 +1,134 b''
1 adding a
2 hg email: option --date not recognized
3 hg email [OPTION]... [DEST]...
4
5 send changesets by email
6
7 By default, diffs are sent in the format generated by hg export,
8 one per message. The series starts with a "[PATCH 0 of N]"
9 introduction, which describes the series as a whole.
10
11 Each patch email has a Subject line of "[PATCH M of N] ...", using
12 the first line of the changeset description as the subject text.
13 The message contains two or three body parts. First, the rest of
14 the changeset description. Next, (optionally) if the diffstat
15 program is installed, the result of running diffstat on the patch.
16 Finally, the patch itself, as generated by "hg export".
17
18 With --outgoing, emails will be generated for patches not
19 found in the destination repository (or only those which are
20 ancestors of the specified revisions if any are provided)
21
22 With --bundle, changesets are selected as for --outgoing,
23 but a single email containing a binary Mercurial bundle as an
24 attachment will be sent.
25
26 Examples:
27
28 hg email -r 3000 # send patch 3000 only
29 hg email -r 3000 -r 3001 # send patches 3000 and 3001
30 hg email -r 3000:3005 # send patches 3000 through 3005
31 hg email 3000 # send patch 3000 (deprecated)
32
33 hg email -o # send all patches not in default
34 hg email -o DEST # send all patches not in DEST
35 hg email -o -r 3000 # send all ancestors of 3000 not in default
36 hg email -o -r 3000 DEST # send all ancestors of 3000 not in DEST
37
38 hg email -b # send bundle of all patches not in default
39 hg email -b DEST # send bundle of all patches not in DEST
40 hg email -b -r 3000 # bundle of all ancestors of 3000 not in default
41 hg email -b -r 3000 DEST # bundle of all ancestors of 3000 not in DEST
42
43 Before using this command, you will need to enable email in your hgrc.
44 See the [email] section in hgrc(5) for details.
45
46 options:
47
48 -a --attach send patches as inline attachments
49 --bcc email addresses of blind copy recipients
50 -c --cc email addresses of copy recipients
51 -d --diffstat add diffstat output to messages
52 -g --git use git extended diff format
53 -f --from email address of sender
54 --plain omit hg patch header
55 -n --test print messages that would be sent
56 -m --mbox write messages to mbox file instead of sending them
57 -o --outgoing send changes not found in the target repository
58 -b --bundle send changes not in target as a binary bundle
59 -r --rev a revision to send
60 -s --subject subject of first message (intro or single patch)
61 -t --to email addresses of recipients
62 --force run even when remote repository is unrelated (with -b)
63 --base a base changeset to specify instead of a destination (with -b)
64 -e --ssh specify ssh command to use
65 --remotecmd specify hg command to run on the remote side
66
67 use "hg -v help email" to show global options
68 adding b
69 hg email: option --date not recognized
70 hg email [OPTION]... [DEST]...
71
72 send changesets by email
73
74 By default, diffs are sent in the format generated by hg export,
75 one per message. The series starts with a "[PATCH 0 of N]"
76 introduction, which describes the series as a whole.
77
78 Each patch email has a Subject line of "[PATCH M of N] ...", using
79 the first line of the changeset description as the subject text.
80 The message contains two or three body parts. First, the rest of
81 the changeset description. Next, (optionally) if the diffstat
82 program is installed, the result of running diffstat on the patch.
83 Finally, the patch itself, as generated by "hg export".
84
85 With --outgoing, emails will be generated for patches not
86 found in the destination repository (or only those which are
87 ancestors of the specified revisions if any are provided)
88
89 With --bundle, changesets are selected as for --outgoing,
90 but a single email containing a binary Mercurial bundle as an
91 attachment will be sent.
92
93 Examples:
94
95 hg email -r 3000 # send patch 3000 only
96 hg email -r 3000 -r 3001 # send patches 3000 and 3001
97 hg email -r 3000:3005 # send patches 3000 through 3005
98 hg email 3000 # send patch 3000 (deprecated)
99
100 hg email -o # send all patches not in default
101 hg email -o DEST # send all patches not in DEST
102 hg email -o -r 3000 # send all ancestors of 3000 not in default
103 hg email -o -r 3000 DEST # send all ancestors of 3000 not in DEST
104
105 hg email -b # send bundle of all patches not in default
106 hg email -b DEST # send bundle of all patches not in DEST
107 hg email -b -r 3000 # bundle of all ancestors of 3000 not in default
108 hg email -b -r 3000 DEST # bundle of all ancestors of 3000 not in DEST
109
110 Before using this command, you will need to enable email in your hgrc.
111 See the [email] section in hgrc(5) for details.
112
113 options:
114
115 -a --attach send patches as inline attachments
116 --bcc email addresses of blind copy recipients
117 -c --cc email addresses of copy recipients
118 -d --diffstat add diffstat output to messages
119 -g --git use git extended diff format
120 -f --from email address of sender
121 --plain omit hg patch header
122 -n --test print messages that would be sent
123 -m --mbox write messages to mbox file instead of sending them
124 -o --outgoing send changes not found in the target repository
125 -b --bundle send changes not in target as a binary bundle
126 -r --rev a revision to send
127 -s --subject subject of first message (intro or single patch)
128 -t --to email addresses of recipients
129 --force run even when remote repository is unrelated (with -b)
130 --base a base changeset to specify instead of a destination (with -b)
131 -e --ssh specify ssh command to use
132 --remotecmd specify hg command to run on the remote side
133
134 use "hg -v help email" to show global options
General Comments 0
You need to be logged in to leave comments. Login now