From: Rene Herman <rene.herman@keyaccess.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: viro@ZenIV.linux.org.uk, w@1wt.eu, david@lang.hm,
sclark46@earthlink.net, johnpol@2ka.mipt.ru, rjw@sisk.pl,
tilman@imap.cc, Valdis.Kletnieks@vt.edu, lkml@rtr.ca,
davem@davemloft.net, jesper.juhl@gmail.com,
yoshfuji@linux-ipv6.org, jeff@garzik.org,
linux-kernel@vger.kernel.org, git@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Reporting bugs and bisection
Date: Tue, 15 Apr 2008 00:18:24 +0200 [thread overview]
Message-ID: <4803D830.7000206@keyaccess.nl> (raw)
In-Reply-To: <20080414133802.4535e4da.akpm@linux-foundation.org>
On 14-04-08 22:38, Andrew Morton wrote:
> On Mon, 14 Apr 2008 21:13:41 +0200
> Rene Herman <rene.herman@keyaccess.nl> wrote:
>
>> Does that mean you're not going to take patches that align the right end of
>> lines in comments? :-(
>
> erm, was that ":-(" supposed to be a ":-)"?
The ":-(" was supposed to add to the implicitly obvious ":-)". That is, was
indeed joking (Al mentioned them) but with a slightly serious undertone:
> I don't like to merge patches which fix typos and spellos and grammaros
> in comments, simply because I'd be buried in the things. I do take such
> fixes for user-visible text (Documentation/, kerneldoc comments and
> printks).
>
> Right-justification of comments would fall rather a long way below
> spelling fixes.
You, particularly, seem to be very good at picking up trivia. I've posted
completely trivial patches from time to time for small things I encounter
while looking at something else. Things at the "are people going to look
funny at me for even bothering or..." level but you picking them up means
it's still useful to post, so I sometimes do.
Now, in fact, Linux as a _whole_ doesn't seem bad at accepting that kind of
small janitorial stuff but I have been noticing some backlash to it as well.
I'm not sure it's worse or better than historically, but the "checkpatch
syndrome" certainly triggers more of it.
Al specifically wanted more new eyes but the way to reward those new eyes is
accepting their small changes. Al also specifically doesn't like those small
changes when at the level of the automated and semi-brainless checkpatch level.
I believe the janitorial work has been over-organized, both through the
kernel-janitors and checkpatch since while these are very useful in guiding
a newbie in _what_ to do they cause "automated" huge tree-wide trivia storms
which people then don't react overly favourable to and the new eyes who did
all that work of generating it all dim again...
Frankly, the kernel really is fairly complex these days when starting at 0.
Much more complex certainly than, say, back in 2.0 or 2.2 days and while
Al's scenario of per-subsystem reviews might be good, I don't believe it's
very realistic. Companies don't pay to have those done and for newbies it's
generally too complex since understanding most parts of the kernel fully,
requires understanding most of the rest kernel rather well also.
So you get the really promising newbies? Yeah, that, or you don't get anyone
and if some promising newbies are building up 137 part checkpatch inspired
patchsets that don't help none.
So, what am I saying (what _am_ I saying?!?) ...
I seemed to observe somewhat of an internal contradiction in Al's message
about new eyes and his dislike of the trivial stuff but the contradiction
only exists if the dislike wouldn't be limited to these kinds of huge trivia
storms. I believe it is, and I furthermore believe that yes, it's
over-organization that causes many new eyes to focus on the brainless aspects.
Now, do those new eyes have many other options when very few (to none) of
the core crowd ever does things like answer question on the kernelnewbies
list? From the established names, I only remember ever seeing Greg KH and
Adrian Bunk there. And I'm _still_ pissed that noone would or could tell me
what was wrong with the legacy CD-ROM driver I and Pekka Enberg were toying
around with a while ago. Frankly, I care a whole lot less about a hundred
sparse warning fixes.
In short -- the kernel in it's current state is already quite complex and if
new eyes are wanted they'll need to be coached more. I'm seeing very little
of that.
Rene.
prev parent reply other threads:[~2008-04-14 22:18 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47FEADCB.7070104@rtr.ca>
[not found] ` <20080413121831.d89dd424.akpm@linux-foundation.org>
[not found] ` <20080413202118.GA29658@2ka.mipt.ru>
[not found] ` <200804132233.50491.rjw@sisk.pl>
[not found] ` <20080413205406.GA9190@2ka.mipt.ru>
[not found] ` <48028830.6020703@earthlink.net>
2008-04-13 23:51 ` Reporting bugs and bisection david
2008-04-14 0:36 ` Jakub Narebski
2008-04-14 4:39 ` Willy Tarreau
2008-04-14 5:39 ` Al Viro
2008-04-14 6:24 ` Andrew Morton
2008-04-14 6:39 ` David Miller
2008-04-14 6:43 ` David Miller
2008-04-14 7:23 ` Al Viro
2008-04-14 7:43 ` Al Viro
2008-04-14 8:04 ` Andrew Morton
2008-04-14 8:30 ` David Miller
2008-04-14 9:06 ` Christoph Hellwig
2008-04-14 9:46 ` Andi Kleen
2008-04-15 5:25 ` Bill Fink
2008-04-14 10:15 ` Andrew Morton
2008-04-14 10:41 ` David Miller
2008-04-14 17:35 ` Roman Shaposhnik
2008-04-14 12:08 ` Adrian Bunk
2008-04-14 14:43 ` Arjan van de Ven
2008-04-14 17:51 ` Andrew Morton
2008-04-14 18:24 ` Arjan van de Ven
2008-04-14 19:30 ` Ilpo Järvinen
2008-04-14 15:54 ` James Morris
2008-04-14 22:01 ` David Miller
2008-04-14 23:05 ` Andrew Morton
2008-04-15 4:55 ` Willy Tarreau
2008-04-15 13:18 ` Work WAS(Re: " jamal
2008-04-15 9:33 ` David Newall
2008-04-15 9:54 ` Michael Kerrisk
2008-04-15 14:04 ` David Newall
2008-04-15 20:51 ` Rafael J. Wysocki
2008-04-16 2:34 ` David Newall
2008-04-16 3:53 ` david
2008-04-16 9:06 ` David Newall
2008-04-16 11:02 ` Andi Kleen
2008-04-16 12:41 ` Stephen Clark
2008-04-16 4:29 ` Willy Tarreau
2008-04-16 12:13 ` Rafael J. Wysocki
2008-04-16 12:15 ` Sverre Rabbelier
2008-04-16 13:26 ` Adrian Bunk
2008-04-16 19:02 ` Andrew Morton
2008-04-16 19:43 ` Sverre Rabbelier
2008-04-16 19:55 ` Adrian Bunk
2008-04-17 13:50 ` J. Bruce Fields
2008-04-17 15:26 ` Adrian Bunk
2008-04-16 19:58 ` Alexey Dobriyan
2008-04-16 20:01 ` Arjan van de Ven
2008-04-16 19:39 ` Sverre Rabbelier
2008-04-16 20:16 ` Adrian Bunk
2008-04-16 20:53 ` Adrian Bunk
2008-04-16 21:05 ` Sverre Rabbelier
2008-04-16 21:25 ` Adrian Bunk
2008-04-16 20:04 ` Willy Tarreau
2008-04-16 20:55 ` Jakub Narebski
2008-04-16 21:17 ` Jesper Juhl
2008-04-17 17:04 ` David Newall
2008-04-17 19:09 ` Rafael J. Wysocki
2008-04-17 19:35 ` Ray Lee
2008-04-17 19:57 ` Sverre Rabbelier
2008-04-17 20:16 ` Al Viro
2008-04-17 20:38 ` Ray Lee
2008-04-17 20:53 ` Al Viro
2008-04-17 21:01 ` Ray Lee
2008-04-14 19:13 ` Rene Herman
2008-04-14 20:38 ` Andrew Morton
2008-04-14 22:18 ` Rene Herman [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=4803D830.7000206@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=jesper.juhl@gmail.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sclark46@earthlink.net \
--cc=tilman@imap.cc \
--cc=viro@ZenIV.linux.org.uk \
--cc=w@1wt.eu \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).