public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Thomas Voss <mail@thomasvoss.com>, linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] CONTRIBUTING: tfix
Date: Fri, 18 Nov 2022 12:24:16 +0100	[thread overview]
Message-ID: <7369d132-409e-34b7-1b44-4bdb795dcd17@gmail.com> (raw)
In-Reply-To: <20221118091727.26874-1-mail@thomasvoss.com>


[-- Attachment #1.1: Type: text/plain, Size: 847 bytes --]

Hi Thomas,

On 11/18/22 10:17, Thomas Voss wrote:
> ---
>   CONTRIBUTING | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/CONTRIBUTING b/CONTRIBUTING
> index 8405f670d..59d980271 100644
> --- a/CONTRIBUTING
> +++ b/CONTRIBUTING
> @@ -71,7 +71,7 @@ Description
>   
>                [patch] shmop.2: Add "(void *)" cast to RETURN VALUE
>   
> -       -  Sign your patch with "Signed-opff-by:".  Read about the "Developer's
> +       -  Sign your patch with "Signed-off-by:".  Read about the "Developer's

Oops.  Patch applied.  :)

Thanks,

Alex

>             Certificate of Origin" at
>             <https://www.kernel.org/doc/Documentation/process/submitting-patches.rst>.
>             When appropriate, other tags documented in that file, such as

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-18 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  9:17 [PATCH] CONTRIBUTING: tfix Thomas Voss
2022-11-18 11:24 ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-09  7:39 Tom Schwindl
2023-03-09 13:07 ` Alejandro Colomar
2023-03-09 15:28 ` G. Branden Robinson
2023-03-11 14:17   ` Tom Schwindl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7369d132-409e-34b7-1b44-4bdb795dcd17@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mail@thomasvoss.com \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox