linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
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: Sun, 23 May 2010 09:26:36 +0300	[thread overview]
Message-ID: <1274595996.8881.42.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1005181936120.3484@lynx>

On Tue, 2010-05-18 at 19:40 -0400, Robert P. J. Day wrote:
> 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.

Hi,

MTD list is not something special, common Linux kernel patch submission
practices apply. So obviously, he signs off his patches, you can review,
test, ack or sign off it. I am not pedantic about which tag to use, but
you can always refer to 'Documentation/SubmittingPatches' and pick the
right one.
 
-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      parent reply	other threads:[~2010-05-23  6:26 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
2010-05-19 11:40   ` Robert P. J. Day
2010-05-23 16:01     ` Artem Bityutskiy
2010-05-23  6:26 ` Artem Bityutskiy [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=1274595996.8881.42.camel@localhost.localdomain \
    --to=dedekind1@gmail.com \
    --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).