[arch-projects] [namcap] [PATCH 4/5] README: Document how to submit patches

[Artur Juraszek]

Vladimir Panteleev writes:

> ---
>  README | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/README b/README
> index 83b406b..b018466 100644
> --- a/README
> +++ b/README
> @@ -21,8 +21,14 @@ Minimal examples (very simple packages forged to exhibit unexpected
>  behaviour from namcap) are also welcome to extend namcap's test suite.
>  
>  If you've a patch (fixing a bug or a new namcap module), then you can send it 
> -to the arch-projects mailing list. Namcap development is managed with git, so
> -git-formatted patches are preferred. 
> +to the arch-projects mailing list.
> +
> +Namcap development is managed with git, so git-formatted patches are preferred.
> +When sending patches to the mailing list, make sure to set a valid
> +subjectprefix, otherwise the email will be rejected by Mailman.  Git can be
> +configured as follows:
> +
> +git config format.subjectprefix namcap] [PATCH'

Looks like a typo, I believe it is?

>  
>  Namcap's source is available on:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-projects/attachments/20200118/13b0e686/attachment.sig>