All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zefan Li <lizefan@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Jason Cooper <jason@lakedaemon.net>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE-TOPIC] Documentation
Date: Tue, 14 Jul 2015 11:56:42 +0800	[thread overview]
Message-ID: <55A4887A.2000806@huawei.com> (raw)
In-Reply-To: <20150713141126.6a522ba6@gandalf.local.home>

On 2015/7/14 2:11, Steven Rostedt wrote:
> On Mon, 13 Jul 2015 17:42:44 +0000
> Jason Cooper <jason@lakedaemon.net> wrote:
> 
>> On Mon, Jul 13, 2015 at 12:37:50PM -0400, Steven Rostedt wrote:
> 
>>> I agree that newbies shouldn't write documentation.
>>
>> I semi-disagree.  Assuming you meant newbies here as you defined below.
> 
> This really shows what the issue with new recruits is all about. Every
> maintainer is different. The Linux kernel is the largest and fastest
> open source project in the world and its amazing how much that everyone
> does agree on. But every maintainer has a slightly different
> perspective of how to do something, and this can be really aggravating
> to a new comer. As it's been said lots of times, maintaining the Linux
> kernel is much like herding cats. And this burden also weighs down on
> new comers, as they try to figure out which type of cat they are
> dealing with. And all cats just happen to be extremely annoying to deal
> with ;-)
> 
> The best we can do is all to try to be patient with those that contact
> us.
> 

I think it's more often that we just ignore them rather than being impatient...

  reply	other threads:[~2015-07-14  3:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 22:38 [Ksummit-discuss] [CORE-TOPIC] Documentation Peter Hüwe
2015-07-12 23:15 ` Julia Lawall
2015-07-14 11:59   ` Mauro Carvalho Chehab
2015-07-13  9:47 ` Alexey Dobriyan
2015-07-13 16:01   ` Randy Dunlap
2015-07-13 16:37   ` Steven Rostedt
2015-07-13 16:46     ` David Woodhouse
2015-07-13 17:35       ` Steven Rostedt
2015-07-13 19:22         ` Peter Hüwe
2015-07-13 19:28       ` Peter Hüwe
2015-07-13 17:42     ` Jason Cooper
2015-07-13 18:11       ` Steven Rostedt
2015-07-14  3:56         ` Zefan Li [this message]
2015-07-13 19:25       ` Peter Hüwe
2015-07-13 22:10       ` Laurent Pinchart
2015-07-13 17:45   ` Jonathan Corbet
2015-07-13 19:46     ` Peter Hüwe
2015-07-14  2:36       ` Jonathan Corbet
2015-07-14  8:40         ` Laurent Pinchart
2015-07-14 11:19           ` Daniel Vetter
2015-07-14 12:43         ` Mauro Carvalho Chehab
2015-07-14 12:53           ` Jonathan Corbet
2015-07-14 13:57           ` Laurent Pinchart
2015-07-14  6:44       ` Johannes Berg
2015-07-13 19:20   ` Peter Hüwe
2015-07-13 23:01     ` Laurent Pinchart
2015-07-13 17:05 ` Lai Jiangshan
2015-07-13 17:42 ` Jonathan Corbet

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=55A4887A.2000806@huawei.com \
    --to=lizefan@huawei.com \
    --cc=dan.carpenter@oracle.com \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rostedt@goodmis.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.