On Fri, Aug 6, 2010 at 8:56 AM, Simon Horman <span dir="ltr"><<a href="mailto:horms@verge.net.au" target="_blank">horms@verge.net.au</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Fri, Aug 06, 2010 at 12:32:08PM +0200, Arnd Bergmann wrote:<br>
> On Friday 06 August 2010, Simon Horman wrote:<br>
> > > Any of us at Nicira could sign off on it. Jesse Gross<br>
> > > <<a href="mailto:jesse@nicira.com" target="_blank">jesse@nicira.com</a>> does the most substantive work on the kernel module<br>
> > > these days, for what it's worth.<br>
> ><br>
> > That seems reasonable to me.<br>
> ><br>
> > How about I get a patch together, sign it off myself (as the person<br>
> > who prepared the patch) and then seek another sign-off before re-posting<br>
> > the patch for merging.<br>
><br>
> I think it would be more sensible the other way round: The way that the<br>
> Certificate of Origin works (see [1]) works, you should put your S-o-b<br>
> below jesse's to say that everything in the patch either came from<br>
> him (or he knows who) or yourself.<br>
<br>
</div>Ok, how about I prepare a patch, and we order the Signed-off-by lines<br>
as you suggest :-)<br></blockquote><div><br></div><div>That sounds good. If you post the patch to the list when you are ready, I can add a signed-off-by line after everything is finalized.</div><div><br></div><div>It seems pretty clear that it will simplify things if we start adding signed-off-by lines to the kernel code in our repository as a routine matter, so I'll begin doing that.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
In related news. I'm was working on a few patches to get the current<br>
code to work with Linus's (post 2.6.35, pre 2.6.35-rc1) tree. Unfortunately<br>
I ran out of Friday before it was done.</blockquote><div><br></div><div>Great, thanks. We'll start looking the patches over so we can integrate them as soon as possible.</div></div>