All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Please add my tree to linux-next
Date: Mon, 05 Dec 2011 14:52:50 +0800	[thread overview]
Message-ID: <4EDC6A42.1090806@redhat.com> (raw)
In-Reply-To: <20111205171207.3b3bc1ad6d99ad7d7c9c0792@canb.auug.org.au>

于 2011年12月05日 14:12, Stephen Rothwell 写道:
> Hi,
> On Mon, 05 Dec 2011 13:40:29 +0800 Cong Wang<amwang@redhat.com>  wrote:
>>
>>>        * submitted under GPL v2 (or later) and include the Contributor's
>>> 	Signed-off-by,
>>
>> When I sent the patches out, they all have my Signed-off-by, but not in the
>> commit logs in my tree. Is this a problem?
>
> Yes, you must have a signed-off-by line for each person who handles the
> patches (in this case just you, since you are also the author).
> Linus (in theory) would not merge your tree if you asked him to if it
> lacked signed-off-by lines (and I will have to drop it if they are not
> added - this will mean rebasing your tree, of course).
>

Ok, I will re-commit those patches with my S-o-b and rebase my tree.

Thanks!

  reply	other threads:[~2011-12-05  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  4:22 Please add my tree to linux-next Cong Wang
2011-12-04 23:09 ` Stephen Rothwell
2011-12-05  5:40   ` Cong Wang
2011-12-05  6:12     ` Stephen Rothwell
2011-12-05  6:52       ` Cong Wang [this message]
2011-12-07  9:35         ` Cong Wang
2011-12-07 10:37           ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2013-10-31 19:39 Robert Richter
2013-10-31 22:35 ` Stephen Rothwell
2013-10-31 23:44   ` Robert Richter

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=4EDC6A42.1090806@redhat.com \
    --to=amwang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.