public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Bryan Wu" <cooloney.lkml@gmail.com>,
	bryan.wu@analog.com, i2c@lm-sensors.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Blackfin I2C/TWI driver: update for 2.6.24 merge  windows
Date: Fri, 19 Oct 2007 13:52:45 +0200	[thread overview]
Message-ID: <20071019135245.1c482589@hyperion.delvare> (raw)
In-Reply-To: <20071019022334.8e88e285.akpm@linux-foundation.org>

Hi Andrew,

On Fri, 19 Oct 2007 02:23:34 -0700, Andrew Morton wrote:
> On Fri, 19 Oct 2007 11:07:50 +0200 Jean Delvare <khali@linux-fr.org> wrote:
> 
> > BTW, as a rule of thumb, I am ignoring patches that are sent to the
> > LKML in addition to the i2c list. If you think that your patch is so
> > important that it has to be send to a list with over 4500 subscribers
> > that sees 120.000 messages each year, then who am I to dare to comment
> > on it?
> > 
> > If you want me to consider your patches as something that needs my
> > attention, send them to the i2c list only, do not add LKML. This is
> > general advice for everyone sending i2c patches, not just you, of
> > course.
> 
> Disagree.  I don't think there's any benefit to anyone for developers to
> hide their stuff on remote mailing lists.

Hiding? These are lists _dedicated_ to the matter.

>                                            Copying lkml increases the
> changes that someone will spot a bug or some improvement and it generally
> keeps people informed as to what's going on.

Sending spam to millions of people increases the chances than someone
will buy your product. Does it make spam a good thing?

> yeah, 120,000 messages/year.  But a lot of them are just noise.  Patches
> are important.

Lot of noise, yes. Counting 1 second on average to process posts you're
not interested in, that's 33 hours a year. This is completely insane
and that's why I unsubscribed from LKML long ago. And the situation is
only getting worse every year. You may fail to realize the problem just
because you aren't completely human ;)

> And I really don't understand this huffy attitude and putting more
> roadblocks in the way of our contributors.

Quite on the contrary, I am trying to educate people into targeting
their posts to the right lists so that they get more appropriate
responses in a shorter time.

In a world where we would have infinite work power and time would grow
on trees, I would be fine with everyone sending everything to every
mailing list. But in the real world, time spent to do one thing isn't
spent on another. If we don't learn, collectively, to target our posts
to the right people, then we end up wasting a significant amount of our
precious time.

>                                             People like Bryan are doing a
> lot of work to improve Linux and most people are (or should be) grateful
> for that and should be prepared to go the extra yard to help them.

My comment is general and absolutely not targeted at Bryan personally.
I thought it was clear. I fully agree that Bryan is a really pleasant
and easy person to work with and I do appreciate his contributions.

-- 
Jean Delvare

  reply	other threads:[~2007-10-19 11:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 13:53 [PATCH] Blackfin I2C/TWI driver: update for 2.6.24 merge windows Bryan Wu
2007-10-18  6:11 ` Bryan Wu
2007-10-19  9:07   ` Jean Delvare
2007-10-19  9:23     ` Bryan Wu
2007-10-19 10:19       ` Jean Delvare
2007-10-19  9:23     ` Andrew Morton
2007-10-19 11:52       ` Jean Delvare [this message]
2007-10-19 12:49     ` Manu Abraham

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=20071019135245.1c482589@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=akpm@linux-foundation.org \
    --cc=bryan.wu@analog.com \
    --cc=cooloney.lkml@gmail.com \
    --cc=i2c@lm-sensors.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