equal
deleted
inserted
replaced
48 The simplest way of send patches is to use the ``hg email`` command available |
48 The simplest way of send patches is to use the ``hg email`` command available |
49 through the *patchbomb* extension of Mercurial. Preferably, patches should be |
49 through the *patchbomb* extension of Mercurial. Preferably, patches should be |
50 *in the message body* of emails. When submitting a revised version of a patch |
50 *in the message body* of emails. When submitting a revised version of a patch |
51 series, a prefix indicating the iteration number ``<n>`` of the series should |
51 series, a prefix indicating the iteration number ``<n>`` of the series should |
52 be added to email subject prefixes; this can be achieved by specifying a |
52 be added to email subject prefixes; this can be achieved by specifying a |
53 ``--flag v<n>`` option to ``hg email`` command. |
53 ``--flag v<n>`` option to ``hg email`` command. If needed you can also use the |
|
54 --in-reply-to option. |
|
55 |
|
56 Examples: |
|
57 |
|
58 hg email --to cubicweb-devel@lists.cubicweb.org --intro -r <start>::<end> |
|
59 hg email --flag V2 --to cubicweb-devel@lists.cubicweb.org -r <start>::<end> |
|
60 |
|
61 Mailing list: https://lists.cubicweb.org/mailman/listinfo/cubicweb-devel |
|
62 Patchbomb extension: https://www.mercurial-scm.org/wiki/PatchbombExtension |
|
63 Good practice on sending email patches: https://www.mercurial-scm.org/wiki/ContributingChanges#Emailing_patches |