diff mbox series

[namcap,4/5] README: Document how to submit patches

Message ID 20200117131931.1746498-4-archlinux@thecybershadow.net
State New
Headers show
Series [namcap,1/5] namcap-devel: Quote arguments | expand

Commit Message

Vladimir Panteleev Jan. 17, 2020, 1:19 p.m. UTC 
---
 README | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

Comments

Emil Velikov via arch-projects Jan. 18, 2020, 12:18 p.m. UTC | #1 
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:
Vladimir Panteleev Jan. 21, 2020, 1:08 p.m. UTC | #2 
Artur Juraszek <artur@juraszek.xyz> writes:

> Vladimir Panteleev writes:
>
>> +git config format.subjectprefix namcap] [PATCH'
>
> Looks like a typo, I believe it is?

Oops, yes, I missed a '. If that's the only problem, please add it
before committing, I'll fix it in v2 otherwise.
diff mbox series

Patch

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'
 
 Namcap's source is available on: