From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Christoph Hellwig <hch@lst.de>,
jsimmons@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] back out fbdev sysfs support
Date: Sat, 14 Feb 2004 18:06:00 +0100 [thread overview]
Message-ID: <20040214170600.GA16147@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0402140857520.13436@home.osdl.org>
On Sat, Feb 14, 2004 at 09:02:12AM -0800, Linus Torvalds wrote:
> Sorry, but at this point I WOULD NOT EVEN TAKE IT ANY MORE.
>
> That's just how I work: if somebody maintains his own tree and builds up a
> lot of patches, that's _his_ problem. I'm not going to replace things
> totally unless there is some really fundamental reason I would have to.
> And quite frankly, the most common "fundamental reason" is that the
> maintainer has not done his job.
>
> I want controlled patches that do one thing at a time. Not a 2GB untested
> dump.
Hey, that's not what I meant. Sorry for the silly language. I'm the
last one to argue in favour of a single big diff. But all the driver
fixes are easily separatable, in fact benh probably still has all the
individual diffs for all the mac drivers.
What I meant is that the FB maintainer should try to get the existing
fixes merged before adding dubious features.
next prev parent reply other threads:[~2004-02-14 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 16:50 [PATCH] back out fbdev sysfs support Christoph Hellwig
2004-02-14 17:02 ` Linus Torvalds
2004-02-14 17:06 ` Christoph Hellwig [this message]
2004-02-14 17:28 ` Dave Jones
2004-02-14 23:02 ` Benjamin Herrenschmidt
2004-02-14 17:58 ` viro
2004-02-14 19:57 ` Paul Mundt
2004-02-14 23:04 ` Benjamin Herrenschmidt
2004-02-16 22:49 ` James Simmons
2004-02-16 22:58 ` Benjamin Herrenschmidt
2004-02-16 23:07 ` James Simmons
2004-02-16 22:44 ` James Simmons
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=20040214170600.GA16147@lst.de \
--to=hch@lst.de \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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