kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: a couple other common patch submission boo boos
Date: Mon, 15 Sep 2014 06:55:42 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1409150648170.3592@localhost> (raw)


  oh, and while i'm here, i'm going to point out a couple other things
you should avoid if you're trying to get your first patch into the
kernel -- unsurprisingly, nick has violated both of these guidelines a
number of times.

  first, good grammar. seriously, good grammar. if you can't use
proper grammar for the single-line "Subject" field, you really have no
business submitting patches.

  and second, your explanation for the patch (what goes into the
commit log) should *match* the patch. in particular, do not claim that
you are fixing an "error" when all you're doing is cleaning up a
*warning*. nick is a major violator of this prime directive -- do not
categorize something as an "error" if it isn't.  end of story.

  and on that note, we return you to the nick krause mailing list.
enjoy.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2014-09-15 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 10:55 Robert P. J. Day [this message]
2014-09-16  7:48 ` a couple other common patch submission boo boos Bjørn Mork

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.LFD.2.11.1409150648170.3592@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).