[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1177620521.6031.2.camel@localhost.localdomain>
Date: Thu, 26 Apr 2007 13:48:41 -0700
From: john stultz <johnstul@...ibm.com>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Peter Keilty <peter.keilty@...com>, linux-ia64@...r.kernel.org,
Eric Whitney <eric.whitney@...com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] ia64: convert to use clocksource code
On Thu, 2007-04-26 at 22:41 +0200, Sam Ravnborg wrote:
> On Thu, Apr 26, 2007 at 04:26:32PM -0400, Peter Keilty wrote:
> > From: Peter Keilty <peter.keilty@...com>
> >
> > Initial ia64 conversion to the generic timekeeping/clocksource code.
> >
> > Signed-off-by: Peter Keilty <peter.keilty@...com>
> > Signed-off-by: John Stultz <johnstul@...ibm.com>
>
> The "Signed-off-by:" should reflect the order in which a path is processed
> with the last submitter at the bottom of the list.
> So if this patch came from John then he should be first in the list
> and since the patch passes you and you submit it you should be in the bottom
> of the list.
>
> And "Signed-off-by:" tell the path that the patch takes. It is not to be used
> to let others say "I have seen it and I think the patch is ok".
> For the latter we have "Acked-by:".
Yea. Its a little odd in this case, because Peter sent me the signed off
code, then I've made tweaks to it and signed it off, then peter picked
that up and has made further improvements.
So I don't think it is inaccurate, but I see how it could be confusing.
Maybe Peter should add an extra signed-off so its more clear?
thanks
-john
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists