public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Stemen <linuxkernel@AdvancedResearch.org>
To: Rik van Riel <riel@conectiva.com.br>,
	Vincent Stemen <linuxkernel@AdvancedResearch.org>
Cc: Mike Galbraith <mikeg@wen-online.de>, linux-kernel@vger.kernel.org
Subject: Re: Plain 2.4.5 VM... (and 2.4.5-ac3)
Date: Wed, 30 May 2001 22:11:00 -0500	[thread overview]
Message-ID: <01053022110000.02370@quark> (raw)
In-Reply-To: <Pine.LNX.4.21.0105301722510.13062-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0105301722510.13062-100000@imladris.rielhome.conectiva>

On Wednesday 30 May 2001 15:30, Rik van Riel wrote:
> On Wed, 30 May 2001, Vincent Stemen wrote:
> > The problem is, that's not true.  These problems are not slipping
> > through because of lack of testers.  As Alan said, the VM problem has
> > been lurking, which means that it was known already.
>
> Fully agreed, it went through because of a lack of hours
> per day and the fact that the priority of developers was
> elsewhere.
>
> For me, for example, the priorities have mostly been with
> bugs that bothered me or that bothered Conectiva's customers.
>
> If you _really_ feel this strongly about the bug, you could
> either try to increase the number of hours a day for all of

I sure wish I could :-).

> us or you could talk to my boss about hiring me as a consultant
> to fix the problem for you on an emergency basis :)
> The other two alternatives would be either waiting until
> somebody gets around to fixing the bug or sending in a patch
> yourself.
>
> Trying to piss off developers has adverse effect on all four
> of the methods above :)
>

Why should my comments piss anybody off?  I am just trying to point
out a problem, as I see it, an offer suggestions for improvement.
Other developers will either agree with me or they wont.
Contributions are not made only through writing code.  I contribute
through code, bug reports, ideas, and suggestions.  I would love to
dive in and try to help fix some of the kernel problems but my hands
are just to full right now.

My comments are not meant to rush anybody and I am not criticizing how
long it is taking.  I know everybody is doing everything they can just
like I am, and they are doing a terrific job.  I am just suggesting a
modification to the way the kernels are distributed that is more like
the early versions that I hoped would allow us to maintain a stable
kernel for distributions and production machines.

- Vincent Stemen


  reply	other threads:[~2001-05-31  3:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  2:32 Plain 2.4.5 VM G. Hugh Song
2001-05-29  4:10 ` Jakob Østergaard
2001-05-29  4:26   ` safemode
2001-05-29  4:38     ` Jeff Garzik
2001-05-29  6:04       ` Mike Galbraith
2001-05-29 14:06       ` Gerhard Mack
2001-05-29  4:46   ` G. Hugh Song
2001-05-29  4:57     ` Jakob Østergaard
2001-05-29  7:13   ` Marcelo Tosatti
2001-05-29  9:10   ` Alan Cox
2001-05-29 15:37     ` elko
2001-05-29 20:09       ` Plain 2.4.5 VM... (and 2.4.5-ac3) Vincent Stemen
2001-05-29 20:16         ` Alan Cox
2001-05-29 21:36           ` Vincent Stemen
2001-05-30  6:02             ` Mike Galbraith
2001-05-30 19:58               ` Vincent Stemen
2001-05-30 20:11                 ` Alan Cox
2001-05-30 20:17                 ` Mike Galbraith
2001-05-31  3:47                   ` Vincent Stemen
2001-05-31  6:18                     ` Mike Galbraith
2001-05-30 20:30                 ` Rik van Riel
2001-05-31  3:11                   ` Vincent Stemen [this message]
     [not found]                 ` <991254700.786.0.camel@tux.bitfreak.net>
2001-05-30 21:59                   ` Vincent Stemen
2001-05-30 20:16             ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2001-05-31 17:23 Benjamin Redelings I

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=01053022110000.02370@quark \
    --to=linuxkernel@advancedresearch.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=riel@conectiva.com.br \
    /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