From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
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,
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: Mon, 14 Apr 2008 03:15:30 -0700 [thread overview]
Message-ID: <20080414031530.2507660d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080414.013058.149905948.davem@davemloft.net>
On Mon, 14 Apr 2008 01:30:58 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Mon, 14 Apr 2008 01:04:12 -0700
>
> > That all sounds good and I expect few would disagree. But if it is to
> > happen, it clearly won't happen by itself, automatically. We will need to
> > force it upon ourselves and the means by which we will do that is process
> > changes. The thing which is being disparaged as "bureaucracy".
> >
> > The steps to be taken are:
> >
> > a) agree that we have a problem
> ...
> > I have thus far failed to get us past step a).
>
> A lot of people, myself included, subconsciously don't want to
> get past step a) because the resulting "bureaucracy" or whatever
> you want to call it is perceived to undercut the very thing
> that makes the Linux kernel fun to work on.
>
> It's still largely free form, loose, and flexible. And that's
> a notable accomplishment considering how much things have changed.
> That feeling is why I got involved in the first place, and I know
> it's what gets other new people in and addicted too.
>
> Nobody is "forced" to do anything, and I notice you used the
> word "force" in d) :-)
OK, I was going to let this pass, but I changed my mind.
You carefully deleted my text so that you could misquote it, thereby
flagrantly misrepresenting everything I said.
Here it is again:
: The steps to be taken are:
:
: a) agree that we have a problem
:
: b) agree that we need to address it
:
: c) identify the day-to-day work practices which will help address it (as
: you have done)
:
: d) identify the process changes which will force us to adopt those practices
:
: e) implement those process changes.
Forcing a discipline upon oneself is totally different from having it
forced upon you by someone else.
Each step will need general agreement and buyin, otherwise none of it will
(or should) work.
next prev parent reply other threads:[~2008-04-14 10:17 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 [this message]
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
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=20080414031530.2507660d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Valdis.Kletnieks@vt.edu \
--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).