public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: ksummit-2008-discuss@lists.linux-foundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Current List of Kernel Summit suggested topics from the discuss list
Date: Fri, 27 Jun 2008 11:11:39 -0700	[thread overview]
Message-ID: <48652D5B.60108@zytor.com> (raw)
In-Reply-To: <200806271035.22856.jbarnes@virtuousgeek.org>

Jesse Barnes wrote:
> If we measure quality using bug metrics, things are pretty hard.

One problem with any metric is that the metric becomes a driving factor 
in itself.  Consider the whole whitespace issue, for example.

As far as the whitespace issue is concerned, we may want to consider 
just setting a flag day -- probably immediately before an -rc1 release 
-- and just run "cleanfile" on the whole tree.  In-flux patches are 
still appliable with "patch -l", and by now we should have enough tools 
to avoid adding new whitespace problems, so we can just kill this issue 
once and for all.

	-hpa

  reply	other threads:[~2008-06-27 18:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 14:41 Current List of Kernel Summit suggested topics from the discuss list James Bottomley
2008-06-27 14:53 ` [Ksummit-2008-discuss] " Arjan van de Ven
2008-06-27 15:09   ` James Bottomley
2008-06-27 15:19     ` Rafael J. Wysocki
2008-06-27 17:35   ` Jesse Barnes
2008-06-27 18:11     ` H. Peter Anvin [this message]
2008-06-27 18:23       ` Jesse Barnes
2008-06-27 15:19 ` Christoph Hellwig
2008-06-27 17:18 ` Jens Axboe
2008-07-03  9:29 ` Arnd Bergmann
2008-07-03 18:27 ` [Ksummit-2008-discuss] " Greg KH
2008-07-03 23:59   ` Stephen Rothwell

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=48652D5B.60108@zytor.com \
    --to=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=ksummit-2008-discuss@lists.linux-foundation.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