From: Adrian Bunk <bunk@kernel.org>
To: Tuomo Valkonen <tuomov@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [poll] Is the megafreeze development model broken?
Date: Mon, 12 Nov 2007 17:56:16 +0100 [thread overview]
Message-ID: <20071112165616.GM9771@stusta.de> (raw)
In-Reply-To: <20071112160254.GA31972@jolt.modeemi.cs.tut.fi>
On Mon, Nov 12, 2007 at 06:02:54PM +0200, Tuomo Valkonen wrote:
> On 2007-11-12 16:20 +0100, Adrian Bunk wrote:
> > The problem is not what the distributions ship, the problem is simply
> > that problems with distribution packaged software should be reported
> > to the distribution, not upstream.
> >
> > And for becoming at least marginally on-topic again:
> > Assuming your "stable base systems" contains the Linux kernel, how would
> > you prevent users from reporting bugs in their ancient kernels [1] here?
>
> You obviously can't prevent them from reporting problems, but you can
> dissuade them from doing that.
Yes, by asking immediately
Is this issue still present with $latest_upstream_version?
If you don't do this for Ion then that's your fault.
> The kernel (and "Linux" in general)
> being rather "generic" and faceless in the sense I mentioned in the
> previous post does work to that end, and users are more aware that
> "it's the Debian kernel", than it's, say, "a Debian-corrupted
> ancient development snapshot of Ion". The Debian kernel packages
> are not even called 'Linux', just 'kernel',
>...
Let's check your statement against reality:
They are called linux-*
>...
> > But the good thing about open source software is that when you believe
> > your ideas are better than what current distributions do you can
> > implement your ideas and create your own distribution.
>
> Haha, the typical FOSS advocate's fallacy. Quote:
>...
Open source development does not work by whining and trying to spread
your opinion through fake "polls" - either you implement what you want
yourself or it won't happen.
That's the simple truth, and it's your time that you waste when you
continue to complain. It also took me a few years until I learned this
lesson.
But an important observation is that when you start something other
people consider worthwhile there will be other people who participate in
what you do, or who even continue it when you decide to switch to other
projects instead.
> Tuomo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-11-12 16:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:56 [poll] Is the megafreeze development model broken? ciol
2007-11-07 23:06 ` Rik van Riel
2007-11-07 23:11 ` ciol
2007-11-08 1:36 ` Adrian Bunk
2007-11-08 20:45 ` ciol
2007-11-08 6:18 ` Stephen Hemminger
2007-11-08 13:38 ` David Newall
2007-11-08 14:26 ` Chris Snook
2007-11-08 20:41 ` ciol
2007-11-09 0:15 ` Chris Snook
2007-11-12 11:09 ` Eric W. Biederman
2007-11-12 13:51 ` Tuomo Valkonen
2007-11-12 15:20 ` Adrian Bunk
2007-11-12 16:02 ` Tuomo Valkonen
2007-11-12 16:56 ` Adrian Bunk [this message]
2007-11-12 17:16 ` Tuomo Valkonen
2007-11-12 17:34 ` Adrian Bunk
2007-11-12 17:42 ` Tuomo Valkonen
2007-11-13 10:11 ` David Newall
2007-11-12 17:37 ` Rogelio M. Serrano Jr.
2007-11-12 17:53 ` Tuomo Valkonen
2007-11-13 12:28 ` Radoslaw Szkodzinski
2007-11-13 13:09 ` Tuomo Valkonen
2007-11-12 16:13 ` Rogelio M. Serrano Jr.
2007-11-12 17:14 ` Adrian Bunk
2007-11-12 17:18 ` Tuomo Valkonen
2007-11-12 23:39 ` Matthias Schniedermeyer
2007-11-13 0:12 ` Tuomo Valkonen
2007-11-12 17:30 ` david
2007-11-12 18:25 ` Rogelio M. Serrano Jr.
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=20071112165616.GM9771@stusta.de \
--to=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tuomov@iki.fi \
/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