From: Stephan von Krawczynski <skraw@ithnet.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18
Date: Tue, 26 Feb 2002 18:50:13 +0100 [thread overview]
Message-ID: <20020226185013.1947fb8f.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0202261412360.1413-100000@duckman.distro.conectiva>
In-Reply-To: <20020226174602.4f4b30bc.skraw@ithnet.com> <Pine.LNX.4.44L.0202261412360.1413-100000@duckman.distro.conectiva>
On Tue, 26 Feb 2002 14:13:05 -0300 (BRT)
Rik van Riel <riel@conectiva.com.br> wrote:
> On Tue, 26 Feb 2002, Stephan von Krawczynski wrote:
>
> > In my eyes, the clean choice would have been 2.4.19 release.
>
> Then make one.
>
> It's just too easy for people to critisise marcelo without
> realising how much work he's putting into 2.4.
This comment was suboptimal, Rik.
There is a group of people that can _make_ one, but there is only one that can _release_ it.
No need to discuss if I am a member of the group, but for sure neither me nor you are _the one_.
So we both can do no more than state our personal opinions on the matter.
Some more thoughts while I am at it:
It is the nature of critics to focus on small bits of the picture. That does not mean the whole picture is teared down just from criticising _some part_ of it.
It is the nature of critics that you can always learn something from it. If it is not about the underlying matter it is at least about the person speaking up.
And: please keep in mind that there are (at least) two major groups in this list: one consisting of people getting paid from distro-(and other-)companies to do something useful about linux - and one consisting of people _not_ getting paid for it. It is very obvious that the lines-of-code-for-patches from single heads inside the second group may be a bit less than from the first. This is not necessarily related to the respective persons' knowledge about linux and related issues.
Regards,
Stephan
> Rik
> --
> Will hack the VM for food.
I see, you know what I am talking about.
next prev parent reply other threads:[~2002-02-26 17:52 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 20:20 Linux 2.4.18 Holzrichter, Bruce
2002-02-25 19:18 ` Marcelo Tosatti
2002-02-24 5:08 ` Daniel Phillips
2002-02-25 20:37 ` DevilKin
2002-02-25 20:45 ` Thomas Glanzmann
2002-02-25 21:29 ` John Stoffel
2002-02-25 21:54 ` Mike Fedyk
2002-02-25 21:57 ` John Stoffel
2002-02-25 22:05 ` David S. Miller
2002-02-25 22:58 ` Bernd Eckenfels
2002-02-26 0:19 ` Harald Arnesen
2002-02-25 22:56 ` Bernd Eckenfels
2002-02-26 0:22 ` Harald Arnesen
2002-02-26 0:28 ` Eric Krout
2002-02-26 3:06 ` Andreas Dilger
2002-02-26 16:46 ` Stephan von Krawczynski
2002-02-26 17:13 ` Rik van Riel
2002-02-26 17:50 ` Stephan von Krawczynski [this message]
2002-02-26 19:42 ` Felix Seeger
2002-02-28 22:25 ` Bill Davidsen
2002-02-25 20:27 ` Christoph Hellwig
[not found] <20020225200618.0FAE82069E@eos.telenet-ops.be>
2002-02-25 19:31 ` Marcelo Tosatti
2002-02-24 5:20 ` Daniel Phillips
2002-02-24 5:28 ` Daniel Phillips
2002-02-25 22:08 ` David S. Miller
2002-02-25 22:14 ` Thomas Duffy
2002-02-25 22:16 ` David S. Miller
2002-02-25 22:28 ` Lars Marowsky-Bree
2002-02-25 22:20 ` Rainer Ellinger
2002-02-25 22:19 ` David S. Miller
2002-02-25 23:01 ` Matthias Andree
2002-02-25 23:08 ` David S. Miller
2002-02-25 23:21 ` Jan Niehusmann
2002-02-25 23:32 ` Matthias Andree
2002-02-26 5:04 ` Bill Davidsen
2002-02-26 5:18 ` H. Peter Anvin
2002-02-26 9:09 ` Matthias Andree
2002-02-25 23:34 ` H. Peter Anvin
2002-02-25 23:55 ` David S. Miller
2002-02-26 1:09 ` David Relson
2002-02-26 13:25 ` Juan Quintela
2002-02-25 22:25 ` H. Peter Anvin
2002-02-25 22:50 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 18:37 Marcelo Tosatti
2002-02-25 18:57 ` Marcelo Tosatti
2002-02-25 20:41 ` Daniel Quinlan
2002-02-25 19:40 ` Marcelo Tosatti
2002-02-25 20:09 ` Hugh Dickins
2002-02-25 19:03 ` Marcelo Tosatti
2002-02-25 21:45 ` Florian Weimer
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=20020226185013.1947fb8f.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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