From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] proposed patch
Date: Tue, 22 Feb 2005 03:55:06 -0800 [thread overview]
Message-ID: <20050222115506.GA13882@phaenix.haell.com> (raw)
In-Reply-To: <20050222074052.GA20208@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
At 2005-02-21T23:40:52-0800, Greg KH <gregkh@gentoo.org> wrote:
> On Mon, Feb 21, 2005 at 07:01:20PM -0800, Drake Wyrm wrote:
> > At 2005-02-21T09:58:45-0800, Greg KH <gregkh@gentoo.org> wrote:
> > > On Mon, Feb 21, 2005 at 08:09:08AM +0100, Johan Swensson wrote:
> > > > I would like to suggest that you add
[...]
> > > No. Get the authors to submit the patch to upstream, and then it
> > > will show up in the Gentoo kernel, as well as all other kernels.
> > > </stock>
> > >
> > > If you submit a bug, it will get marked with the same response...
[...]
> > but this one is kept out of the main kernel tree for political
> > reasons.
>
> And, because of that, I will always defer to the upstream kernel
> maintainers, like I would hope that you also would.
We certainly have a difference of opinion on that point. I tend to have
an instintive negative reaction toward technical decisions influenced by
political motives.
> Are you willing to put the time and effort in to maintain, forward
> port, and handle all possible bug reports in the kernel area that is
> touched by this patch? I didn't think so :)
This is actually an excellent illustration of my point. The patch I
mentioned as an example changes almost nothing. It adds one file and
touches the makefiles so that the build process notices it. Its
inclusion would be completely benign.
All I'm trying to say is that, while a critical eye should be placed on
patches considered for the kernel, a stubborn refusal to even consider
changes may be excessive.
--
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
--Ghost in the Shell
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2005-02-22 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36acd65c050220230928e76206@mail.gmail.com>
2005-02-21 10:34 ` [gentoo-dev] proposed patch Aaron Walker
2005-02-21 17:58 ` Greg KH
2005-02-22 3:01 ` Drake Wyrm
2005-02-22 7:40 ` Greg KH
2005-02-22 11:55 ` Drake Wyrm [this message]
2005-02-22 14:09 ` Collins Richey
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=20050222115506.GA13882@phaenix.haell.com \
--to=wyrm@haell.com \
--cc=gentoo-dev@lists.gentoo.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