From: Adrian Bunk <bunk@stusta.de>
To: Al Boldi <a1426z@gawab.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to improve the quality of the kernel?
Date: Thu, 21 Jun 2007 15:07:37 +0200 [thread overview]
Message-ID: <20070621130737.GN12950@stusta.de> (raw)
In-Reply-To: <200706210626.20429.a1426z@gawab.com>
On Thu, Jun 21, 2007 at 06:26:20AM +0300, Al Boldi wrote:
> Adrian Bunk wrote:
> > On Mon, Jun 18, 2007 at 06:55:47AM +0300, Al Boldi wrote:
> > > Michal Piotrowski wrote:
> > > > On 18/06/07, Al Boldi <a1426z@gawab.com> wrote:
> > > > > Bartlomiej Zolnierkiewicz wrote:
> > > > > > On Sunday 17 June 2007, Andrew Morton wrote:
> > > > > > > We of course do want to minimise the amount of overhead for each
> > > > > > > developer. I'm a strong believer in specialisation: rather than
> > > > > > > requiring that *every* developer/maintainer integrate new steps
> > > > > > > in their processes it would be better to allow them to proceed
> > > > > > > in a close-to-usual fashion and to provide for a specialist
> > > > > > > person (or team) to do the sorts of things which you're thinking
> > > > > > > about.
> > > > > >
> > > > > > Makes sense... however we need to educate each and every developer
> > > > > > about importance of the code review and proper recognition of
> > > > > > reviewers.
> > > > >
> > > > > That's as easy to manage as is currently done with rc-regressions.
> > > >
> > > > Are you a volunteer?
> > >
> > > Probably not, as this task requires a real PRO!
> > >...
> >
> > That's wrong.
> >
> > We are talking about _tracking_.
> >
> > I'm not sure whether it makes much sense, and it would cost an enormous
> > amount of time, but tracking patches should be possible without any
> > knowledge of the kernel.
>
> If that's really true, which I can't imagine, then the proper way forward
> would probably involve a fully automated system.
If you consider any kind of patch tracking valuable, you should either
do it yourself or write the tool yourself. In both cases, the
interesting parts would be how to integrate it into the workflow of
kernel development without creating extra work for anyone and how to get
the information into the got commits.
"requires a real PRO" and "would probably involve" sound like cheap
phrases for avoiding doing any work yourself.
Talk is cheap, but unless YOU will do it your emails will only be a
waste of bandwidth.
> Thanks!
> Al
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-06-21 13:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 22:41 How to improve the quality of the kernel? Al Boldi
2007-06-17 22:55 ` Michal Piotrowski
2007-06-18 3:55 ` Al Boldi
2007-06-20 21:34 ` Adrian Bunk
2007-06-21 3:26 ` Al Boldi
2007-06-21 13:07 ` Adrian Bunk [this message]
2007-06-21 13:41 ` Al Boldi
2007-06-21 13:57 ` Adrian Bunk
2007-06-21 21:33 ` Al Boldi
2007-06-22 11:24 ` Adrian Bunk
2007-06-21 15:48 ` Stefan Richter
-- strict thread matches above, loose matches on Subject: below --
2007-04-29 17:50 Linux 2.6.21 Linus Torvalds
2007-06-14 6:29 ` regression tracking (Re: Linux 2.6.21) Oleg Verych
2007-06-15 23:20 ` Linus Torvalds
2007-06-15 23:42 ` Adrian Bunk
2007-06-16 1:32 ` Oleg Verych
2007-06-16 12:23 ` Stefan Richter
2007-06-17 0:44 ` Adrian Bunk
2007-06-17 9:41 ` [PATCH] (Re: regression tracking (Re: Linux 2.6.21)) Michal Piotrowski
2007-06-17 12:45 ` Adrian Bunk
2007-06-17 13:17 ` Michal Piotrowski
2007-06-17 14:29 ` How to improve the quality of the kernel? Adrian Bunk
2007-06-17 16:15 ` Michal Piotrowski
2007-06-17 16:26 ` Stefan Richter
2007-06-17 16:47 ` Michal Piotrowski
2007-06-17 18:24 ` Adrian Bunk
2007-06-17 18:44 ` Stefan Richter
2007-06-17 18:50 ` Natalie Protasevich
2007-06-22 12:01 ` Markus Rechberger
2007-06-22 14:19 ` Stefan Richter
2007-06-22 15:25 ` Oleg Verych
2007-06-17 17:31 ` Rafael J. Wysocki
2007-06-17 17:42 ` Natalie Protasevich
2007-06-17 18:16 ` Rafael J. Wysocki
2007-06-17 19:31 ` Adrian Bunk
2007-06-17 18:53 ` Bartlomiej Zolnierkiewicz
2007-06-17 18:52 ` Andrew Morton
2007-06-17 19:18 ` Rafael J. Wysocki
2007-06-17 19:33 ` Carlo Wood
2007-06-17 20:00 ` Stefan Richter
2007-06-17 20:10 ` Michal Piotrowski
2007-06-17 21:49 ` Bartlomiej Zolnierkiewicz
2007-06-17 23:15 ` Stefan Richter
2007-06-18 0:22 ` Bartlomiej Zolnierkiewicz
2007-06-18 0:32 ` Stefan Richter
2007-06-18 5:09 ` Andrew Morton
2007-06-18 13:23 ` Fortier,Vincent [Montreal]
2007-06-18 22:31 ` Natalie Protasevich
2007-06-18 22:41 ` Martin Bligh
2007-06-18 22:56 ` Natalie Protasevich
2007-06-18 23:59 ` Martin Bligh
2007-06-19 0:09 ` Linus Torvalds
2007-06-19 0:24 ` Natalie Protasevich
2007-06-19 0:42 ` Martin Bligh
2007-06-19 0:55 ` Natalie Protasevich
2007-06-19 1:10 ` Martin Bligh
2007-06-19 1:51 ` Fortier,Vincent [Montreal]
2007-06-19 2:27 ` Natalie Protasevich
2007-06-19 11:06 ` Stefan Richter
2007-06-17 23:15 ` Rafael J. Wysocki
2007-06-18 1:04 ` Bartlomiej Zolnierkiewicz
2007-06-17 18:54 ` Michal Piotrowski
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=20070621130737.GN12950@stusta.de \
--to=bunk@stusta.de \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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