All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Sameer Rahmani <lxsameer@gnu.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
	Joe Perches <joe@perches.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust to kobject doc ReST conversion
Date: Wed, 4 Mar 2020 22:37:08 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2003042230100.2698@felia> (raw)
In-Reply-To: <959e8f4c-9ff6-4388-9b6f-23f6e548e9e5@gnu.org>



On Wed, 4 Mar 2020, Sameer Rahmani wrote:
> 
> Thanks for the fix. It looks good to me
> 
> 

Sameer, in the kernel community, there is the convention to acknowledge a 
patch with responses, such as Acked-by or Reviewed-by. Maintainer scripts 
then allow the maintainer to pick those up automatically from the 
responses. So, you would respond in a new line with "Acked-by: your full 
name <your email address>".

You can read more on that here:

https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by

I hope this helps and is interesting to you.

Thanks for your review and quick response to my patch,

Lukas

WARNING: multiple messages have this Message-ID (diff)
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Sameer Rahmani <lxsameer@gnu.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
	Joe Perches <joe@perches.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust to kobject doc ReST conversion
Date: Wed, 04 Mar 2020 21:37:08 +0000	[thread overview]
Message-ID: <alpine.DEB.2.21.2003042230100.2698@felia> (raw)
In-Reply-To: <959e8f4c-9ff6-4388-9b6f-23f6e548e9e5@gnu.org>



On Wed, 4 Mar 2020, Sameer Rahmani wrote:
> 
> Thanks for the fix. It looks good to me
> 
> 

Sameer, in the kernel community, there is the convention to acknowledge a 
patch with responses, such as Acked-by or Reviewed-by. Maintainer scripts 
then allow the maintainer to pick those up automatically from the 
responses. So, you would respond in a new line with "Acked-by: your full 
name <your email address>".

You can read more on that here:

https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by

I hope this helps and is interesting to you.

Thanks for your review and quick response to my patch,

Lukas

  reply	other threads:[~2020-03-04 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 11:08 [PATCH] MAINTAINERS: adjust to kobject doc ReST conversion Lukas Bulwahn
2020-03-04 11:08 ` Lukas Bulwahn
2020-03-04 11:57 ` Sameer Rahmani
2020-03-04 11:57   ` Sameer Rahmani
2020-03-04 21:37   ` Lukas Bulwahn [this message]
2020-03-04 21:37     ` Lukas Bulwahn
2020-03-10 17:30 ` Jonathan Corbet
2020-03-10 17:30   ` Jonathan Corbet

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=alpine.DEB.2.21.2003042230100.2698@felia \
    --to=lukas.bulwahn@gmail.com \
    --cc=corbet@lwn.net \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lxsameer@gnu.org \
    --cc=rdunlap@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.