From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Documentation/patch-tags v3
Date: Fri, 12 Oct 2007 00:11:30 +0200 [thread overview]
Message-ID: <470E9F92.1030604@s5r6.in-berlin.de> (raw)
In-Reply-To: <1192139467.7899.55.camel@heimdal.trondhjem.org>
Trond Myklebust wrote:
> On Thu, 2007-10-11 at 23:21 +0200, Stefan Richter wrote:
>> 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.
>
> In that case the reviewer should be made part of the forwarding chain,
> and it should be made clear to whoever is upstream that this is a patch
> that has not been modified since it was reviewed.
It's more comfortable for the reviewer to send a mail reply with the tag.
But modifications after review are a problem either way. (If the
modifications are minor, add a description below the Reviewed-by and
sign off below that additional description. If they are major, drop the
Reviewed-by. However, a follow-up patch instead of modifying the
reviewed patch should be considered and may be suitable in many cases,
since a patch which passed review should already be fine for commit on
its own.)
>> > Being sure of something and making guarantees are different things.
>
> To a lawyer, yes. To everyone else, no, and the GPL already tells you
> that you are given no warranties.
OK.
--
Stefan Richter
-=====-=-=== =-=- -=-==
http://arcgraph.de/sr/
prev parent reply other threads:[~2007-10-11 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 20:16 Jonathan Corbet
2007-10-11 20:50 ` Trond Myklebust
2007-10-11 21:07 ` Randy Dunlap
2007-10-11 21:21 ` Stefan Richter
2007-10-11 21:51 ` Trond Myklebust
2007-10-11 22:11 ` Stefan Richter [this message]
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=470E9F92.1030604@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®