All of lore.kernel.org
 help / color / mirror / Atom feed
From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: dev process - reduce mistakes
Date: Wed, 19 Sep 2018 09:35:36 +1000	[thread overview]
Message-ID: <20180918233536.GC16921@eros> (raw)

Hi,

I'm after some advice from those more experienced with [kernel]
development please.

What systems do you have in place to help catch mistakes?  In other
words; what processes do you use when coding and submitting patches to
help eliminate simple mistakes?  So far my best method is getting a
patch [set] ready then waiting until the next day before reviewing the
set and submitting.  I am facing an issue where by when doing (less than
super interesting) large patch sets (like docs fixes) that by the time I
get to the final review my eyes glaze over and I'm still missing
mistakes.

My future maintainers will thank you ;)


thanks,
Tobin.

             reply	other threads:[~2018-09-18 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 23:35 Tobin C. Harding [this message]
2018-09-19  0:01 ` dev process - reduce mistakes valdis.kletnieks at vt.edu
2018-09-19  2:15   ` Tobin C. Harding
2018-09-19  2:01 ` Cindy-Sue Causey
2018-09-25  6:03   ` Tobin C. Harding

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=20180918233536.GC16921@eros \
    --to=me@tobin.cc \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.