public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Valdis.Kletnieks@vt.edu
Cc: 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:15:48 +0800	[thread overview]
Message-ID: <5101EAD4.9080309@asianux.com> (raw)
In-Reply-To: <30811.1359070263@turing-police.cc.vt.edu>

Hello Valdis Kletnieks:

  thank you for your reply, firstly.

  also thank public kernel to provide this additional managerial services to members
    (for me, "replying member's plan" belongs to managerial services)

  for "[Consult]" title mails.
    next time, I should use "Hello all" instead of " Hello 'each real-name' ".
      (for no one has duty to must reply it, especially every one has his or her own work)


于 2013年01月25日 07:31, Valdis.Kletnieks@vt.edu 写道:
> 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. ...

  I guess, one of his main work is for checking and integrating another patches.
    (also have to spend much time to communicate with many members for their patches)

  I guess, some of his goal for internal are:
    to let another members to provide correct contributes (patch should be checked)
    and also keep them with efficiency and sustainable.


> More realistic goal:
> 
> 1) Get a patch accepted.
> 2) Get another patch accepted.
> 3) Re-evaluate how many patches you can actually do.

  thank you for your advice.
  I should be mainly focused on current actions and results.


additional consult:

  does "accepted" means:
    the patch is applied in "tovalds" or "next-*" tree (another trees are not count)
    the patch type is "Signed-of-by" (Reported-by, ... are not count)
    the patch content is for new feature or bug fix (comments, ... are not count)


  Regards


-- 
Chen Gang

Asianux Corporation

      parent reply	other threads:[~2013-01-25  2:15 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
2013-01-26  8:17       ` Chen Gang F T
2013-01-25  2:15   ` Chen Gang [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=5101EAD4.9080309@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --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