From: Wolfram Sang <w.sang@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: how to pre-screen patch submissions from a newbie janitor?
Date: Wed, 19 May 2010 02:01:37 +0200 [thread overview]
Message-ID: <20100519000137.GA18592@pengutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1005181936120.3484@lynx>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
> however, since he's new to patch creation and submission, i offered
> to "vet" his patches first. i realize that my vetting carries no
> weight on the MTD list, but given that i've submitted lots and lots of
> patches elsewhere, i can still at least sanity check what he comes up
> with before it hits the list.
>
> is there a canonical signage for that nowadays? is it "Reviewed-By"
> or something like that? so that by the time it gets to the MTD list,
> he would have done the "Signed-Off-By" and i'd sign off as a reviewer.
> is that the way it works? or is there an alternative? thanks.
Yes, that sounds like a good case for Reviewed-by. It will surely help these
patches knowing there is somebody with experience who already had a look at
(and in that case probably build-tested) them.
Looking forward to the series,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-05-19 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 23:40 how to pre-screen patch submissions from a newbie janitor? Robert P. J. Day
2010-05-19 0:01 ` Wolfram Sang [this message]
2010-05-19 11:40 ` Robert P. J. Day
2010-05-23 16:01 ` Artem Bityutskiy
2010-05-23 6:26 ` Artem Bityutskiy
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=20100519000137.GA18592@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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;
as well as URLs for NNTP newsgroup(s).