Linux Documentation
 help / color / mirror / Atom feed
From: Himanshu Jha <himanshujha199640@gmail.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>,
	jic23@kernel.org, linux-iio@vger.kernel.org
Cc: joe@perches.com, gregkh@linuxfoundation.org, apw@canonical.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	niklas.cassel@linaro.org, corbet@lwn.net,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] docs: fix Co-Developed-by docs
Date: Fri, 14 Dec 2018 23:42:43 +0530	[thread overview]
Message-ID: <20181214181240.GA20094@himanshu-Vostro-3559> (raw)
In-Reply-To: <1544808928-20002-2-git-send-email-jorge.ramirez-ortiz@linaro.org>

On Fri, Dec 14, 2018 at 06:35:27PM +0100, Jorge Ramirez-Ortiz wrote:
> The accepted terminology will be Co-developed-by therefore losing the
> capital letter from now on.
> 
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
> ---

Thanks. ACK!

Finally, the discussion converged at somepoint.

FYI, Cc Jonathan Cameron + IIO list.

>  Documentation/process/submitting-patches.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index c091710..30dc00a 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -510,7 +510,7 @@ tracking your trees, and to people trying to troubleshoot bugs in your
>  tree.
>  
>  
> -12) When to use Acked-by:, Cc:, and Co-Developed-by:
> +12) When to use Acked-by:, Cc:, and Co-developed-by:
>  -------------------------------------------------------
>  
>  The Signed-off-by: tag indicates that the signer was involved in the
> @@ -543,7 +543,7 @@ person it names - but it should indicate that this person was copied on the
>  patch.  This tag documents that potentially interested parties
>  have been included in the discussion.
>  
> -A Co-Developed-by: states that the patch was also created by another developer
> +A Co-developed-by: states that the patch was also created by another developer
>  along with the original author.  This is useful at times when multiple people
>  work on a single patch.  Note, this person also needs to have a Signed-off-by:
>  line in the patch as well.
> -- 
> 2.7.4
> 

-- 
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication
Guru Tegh Bahadur Institute of Technology

  reply	other threads:[~2018-12-14 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 17:35 [PATCH 0/2] Fix Co-Developed-by Jorge Ramirez-Ortiz
2018-12-14 17:35 ` [PATCH 1/2] docs: fix Co-Developed-by docs Jorge Ramirez-Ortiz
2018-12-14 18:12   ` Himanshu Jha [this message]
2018-12-14 17:35 ` [PATCH 2/2] checkpatch: add Co-developed-by to signature tags Jorge Ramirez-Ortiz
2018-12-14 20:16   ` Andrew Morton
2018-12-14 20:58     ` Himanshu Jha
2018-12-15 17:45     ` Joe Perches

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=20181214181240.GA20094@himanshu-Vostro-3559 \
    --to=himanshujha199640@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=joe@perches.com \
    --cc=jorge.ramirez-ortiz@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niklas.cassel@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox