Messages in this thread | | | Date | Mon, 17 Jun 2013 15:00:04 +0200 | From | Peter Zijlstra <> | Subject | Re: [patch v8 3/9] sched: set initial value of runnable avg for new forked task |
| |
On Mon, Jun 17, 2013 at 02:39:53AM -0700, Paul Turner wrote: > I actually did read it before, and still wasn't sure of the right tag to use. > > "13) When to use Acked-by: and Cc: > > The Signed-off-by: tag indicates that the signer was involved in the > development of the patch, or that he/she was in the patch's delivery path. > > If a person was not directly involved in the preparation or handling of a > patch but wishes to signify and record their approval of it then they can > arrange to have an Acked-by: line added to the patch's changelog." > https://www.kernel.org/doc/Documentation/SubmittingPatches > > Acked-By seemed to fail the direct involvement test. > The definition of "delivery path" is not clear; is this strictly by > inputs to Linus' tree or recipients of the original patch?
The way I interpret the delivery path is when its part of a bigger grouping. The author is always the first SOB, if the patch series isn't by the same author then he who compiles the aggregate work adds his SOB.
Similar for (sub)maintainers passing it onwards towards Linus. I compile batches of patch series and feed them to Ingo, Ingo stuffs the lot into -tip and feeds them to Linus.
So supposing you wrote a patch, gave it to Alex who composed the bigger series, which I picked up and handed to Ingo we'd get something like:
SoB: PJT SoB: Alex SoB: PeterZ SoB: Mingo
and then when Linus pulls the lot he could add his SOB too, although looking at git history he typically doesn't add his sob to each and everything he pulls.
But yes, I see where the confusion stems from.
> Is Reviewed-By always more appropriate here?
Yes, or even Acked would work. The difference between reviewed and acked is the level of involvement. An ack is for something you glanced over and generally agree with, a review is for something you looked at in minute detail.
Then there's some people (and I tend to lean towards this) who can't be bothered with that distinction too much and simply always use ack.
| |