public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Chris Boot <bootc@bootc.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] un petite hack: /proc/*/ctl
Date: Wed, 30 Nov 2005 22:23:50 +0100	[thread overview]
Message-ID: <20051130212350.GV11266@alpha.home.local> (raw)
In-Reply-To: <20051130102111.GK9949@vanheusden.com>

On Wed, Nov 30, 2005 at 11:21:11AM +0100, Folkert van Heusden wrote:
> > > Not that I'm seriously proposing patch for inclusion.
> > so please don't pollute the list with useless patches that take time
> > to review.
> 
> Are you theo de raadt's nephew?

not at all. It's just that patches on the list take more and more time
to check, we're around something like 1 patch for 5 mails. And when the
author himself suggests that the patch is not for inclusion, it wastes
time. However, I agree that Alexey announced it as [RFC] and not [PATCH],
so he proceeded correctly and I was wrong to yell at him (that's why I
apologised when I noticed this). But generally speaking, I do not find
it very constructive to send random work in which even the author does
not believe. It only lowers the SNR.

> Folkert van Heusden

Regards,
Willy


  reply	other threads:[~2005-11-30 21:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29  0:28 [RFC] un petite hack: /proc/*/ctl Alexey Dobriyan
2005-11-29  0:23 ` Chris Boot
2005-11-29  1:33   ` Alexey Dobriyan
2005-11-29  5:48     ` Willy Tarreau
2005-11-29  5:53       ` Willy Tarreau
2005-11-29  7:26         ` Denis Vlasenko
2005-11-30 10:21       ` Folkert van Heusden
2005-11-30 21:23         ` Willy Tarreau [this message]
2005-12-09 14:24           ` Jan Engelhardt
2005-12-15  3:58             ` Kyle Moffett

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=20051130212350.GV11266@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=adobriyan@gmail.com \
    --cc=bootc@bootc.net \
    --cc=folkert@vanheusden.com \
    --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