From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Xuetao Guan <gxt@pku•edu.cn>
Cc: Chen Gang <gang.chen.5i5j@gmail•com>,
Guan Xuetao <gxt@mprc•pku.edu.cn>,
linux-next@vger•kernel.org
Subject: Re: 回复： Re: [Consult] About only one Signed-of-by for the patches
Date: Wed, 28 May 2014 08:43:04 +1000 [thread overview]
Message-ID: <20140528084304.22a1a6c8@canb.auug.org.au> (raw)
In-Reply-To: <458532278.27889.1401167250372.JavaMail.root@bj-mail03.pku.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Hi,
On Tue, 27 May 2014 13:07:30 +0800 (CST) Xuetao Guan <gxt@pku•edu.cn> wrote:
>
>
> ----- Stephen Rothwell <sfr@canb•auug.org.au> 写道：
> > Hi Chen,
> >
> > On Tue, 27 May 2014 09:23:38 +0800 Chen Gang <gang.chen.5i5j@gmail•com> wrote:
> > >
> > > I find some of patches are only Signed-of-by me, are they OK?
> >
> > Actually, this one is not OK. Anyone who handles a patch needs to add a
> > Signed-off-by. In the case below, that patch was commited to the tree
> > by Guan Xuetao <gxt@mprc•pku.edu.cn>, so there needs to be a
> > Signed-off-by from them as well.
> >
> > The same is true for all the commits in the unicore32 tree ...
>
> Ok, I see.
>
> Then, do I need to reply each mail with my sob? Or only replace acked-by by sob for all commits in my tree?
You do not need to reply to each email, but any patch that you send on
to Linus (or someone else) needs to have your Signed-off-by. Please
read the "Developer's Certificate of Origin" in section 12 of
Documentation/SubmittingPatches.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-27 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 1:23 [Consult] About only one Signed-of-by for the patches Chen Gang
2014-05-27 1:34 ` Stephen Rothwell
2014-05-27 1:50 ` Chen Gang
2014-05-27 5:07 ` 回复： " Xuetao Guan
2014-05-27 22:43 ` Stephen Rothwell [this message]
2014-05-28 0:00 ` 回复： " Xuetao Guan
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=20140528084304.22a1a6c8@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=gang.chen.5i5j@gmail$(echo .)com \
--cc=gxt@mprc$(echo .)pku.edu.cn \
--cc=gxt@pku$(echo .)edu.cn \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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