public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Valdis.Kletnieks@vt.edu
Cc: Chen Gang <gang.chen@asianux.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Consult] Plan: personal contributes plan for 2013
Date: Thu, 24 Jan 2013 21:14:37 -0500	[thread overview]
Message-ID: <20130125021437.GA28908@thunk.org> (raw)
In-Reply-To: <30811.1359070263@turing-police.cc.vt.edu>

On Thu, Jan 24, 2013 at 06:31:03PM -0500, Valdis.Kletnieks@vt.edu wrote:
> >
> > 10 patches per month: (at least)
> 
> Even Dave Miller only averages 12-15 patches a month, and he does it
> for a living, and they're all in the one part of the kernel he
> maintains.  It's going to be a really hard time for a newcomer to
> get up to speed enough to produce a useful and usable patch every 3
> days on the average, especially across multiple areas of the kernel.

Just to be curious, I checked the number of commits I've done in the
past 12 months, and it's 99, for an average of a bit over 8 patches a
month.  (via "git log --author=tytso --since="1 year ago" --oneline |
wc -l")

More importantly, it's important to shoot for quality, not quantity.
10 patches a month which fixes whitespaces in code that you're not
touching anyway just generates work for maintainers without materially
improving the quality of the kernel.

	      				- Ted

  reply	other threads:[~2013-01-25  2:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 11:32 [Consult] Plan: personal contributes plan for 2013 Chen Gang
2013-01-23 14:23 ` Greg KH
2013-01-24  1:13   ` Chen Gang
2013-01-24 23:31 ` Valdis.Kletnieks
2013-01-25  2:14   ` Theodore Ts'o [this message]
2013-01-25  2:30     ` Chen Gang
2013-01-26  8:17       ` Chen Gang F T
2013-01-25  2:15   ` Chen Gang

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=20130125021437.GA28908@thunk.org \
    --to=tytso@mit.edu \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=gang.chen@asianux.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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