From: Chen Gang <gang.chen@asianux.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Valdis.Kletnieks@vt.edu, 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: Fri, 25 Jan 2013 10:30:03 +0800 [thread overview]
Message-ID: <5101EE2B.3080004@asianux.com> (raw)
In-Reply-To: <20130125021437.GA28908@thunk.org>
于 2013年01月25日 10:14, Theodore Ts'o 写道:
> 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")
>
thank you very much for your information which I can according to.
it is quite valuable for me to make my plan.
> 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.
>
really necessary to give enough limitations (this is just my plan does):
patch contents: which sub-system, API (document), architecture, ...
patch type: functional features or none-functional features
for non-functional features:
bug fix: memory overflow, resource management ...
API: comments, documents, MAINTAINERS, ...
others: beautify code, ...
marked as: Reported-by or Signed-of-by, ...
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-01-25 2:30 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
2013-01-25 2:30 ` Chen Gang [this message]
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=5101EE2B.3080004@asianux.com \
--to=gang.chen@asianux.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.