From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: how to pre-screen patch submissions from a newbie janitor?
Date: Tue, 18 May 2010 19:40:57 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1005181936120.3484@lynx> (raw)
not that long ago, i suggested cleaning up the MTD Kconfig/Makefile
structure since there was some definite redundancy in the inclusion of
source files and subdirectories. now, i could whip up those patches
myself and submit them, but i have a local friend who's itching to get
start doing some simple kernel work and submitting some patches, and
he's more than smart enough to do what i described above.
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.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2010-05-18 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 23:40 Robert P. J. Day [this message]
2010-05-19 0:01 ` how to pre-screen patch submissions from a newbie janitor? Wolfram Sang
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=alpine.DEB.2.00.1005181936120.3484@lynx \
--to=rpjday@crashcourse.ca \
--cc=linux-mtd@lists.infradead.org \
/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