Trond Myklebust wrote:Does a technical review include a review of licensing and copyright issues? (It doesn't seem to be a big issue though if the submitter signed off on it, like he should.) Anybody in the patch forwarding chain (author, maintainers... usually the latter) can add Acked-by and Tested-by, based on incoming feedback. The feedback may have explicitly stated an Acked-by or Tested-by or may have said something equivalent. (In case of Tested-by, an appropriate description of how was tested should have been sent. An explicit Tested-by from the tester himself is moot then.) Reviewed-by is a different beast. If Jon's definition of Reviewed-by (or another definition) is "officially" adopted, people in the patch forwarding chain should only add this tag if the reviewer sent it explicitly in his response. Unlike with Acked-by and Tested-by, we must not guess whether a reviewer wants to have his Reviewed-by added. [...] Being sure of something and making guarantees are different things. -- Stefan Richter -=====-=-=== =-=- -=-== http://arcgraph.de/sr/ -
| Al Boldi | Re: [ck] Re: [ANNOUNCE] RSDL completely fair starvation free interactive cpu sched... |
| Ingo Molnar | Re: [patch] sched_clock(): cleanups |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Denys Vlasenko | [PATCH 1/2] bnx2: factor out gzip unpacker |
