On 18-02-23 00:38:56, Daniel Axtens wrote: > Make this match parser.py > > Signed-off-by: Daniel Axtens <[email protected]> > > -- > > To test, this patch is being sent with X-Patchwork-Ignore: xyzzy > You should see it in Patchwork and on the list. Another patch will > be sent with X-P-H ignore, which should appear on the list only. > --- > docs/usage/headers.rst | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/docs/usage/headers.rst b/docs/usage/headers.rst > index 8741d9c18a44..2b0f4666ba29 100644 > --- a/docs/usage/headers.rst > +++ b/docs/usage/headers.rst > @@ -5,16 +5,16 @@ Patchwork provides a number of special email headers to > control how a patch is > handled when it is received. The examples provided below use > `git-send-email`, > but custom headers can also be set when using tools like `mutt`. > > -`X-Patchwork-Ignore` > +`X-Patchwork-Hint` > > - Valid values: * > + Valid values: ignore > > - When set, the mere presence of this header will ensure the provided email > is > - not parsed by Patchwork. For example: > + When set, the this header will ensure the provided email is not
^^^^^^^^
> + parsed by Patchwork. For example:
>
> .. code-block:: shell
>
> - $ git send-email --add-header="X-Patchwork-Ignore: test" master
> + $ git send-email --add-header="X-Patchwork-Hint: ignore" master
>
> `X-Patchwork-Delegate`
>
> --
> 2.14.1
signature.asc
Description: Digital signature
_______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
