From: Peter Zijlstra <peterz@infradead.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [git pull] drm patches for 2.6.27 final
Date: Mon, 25 Aug 2008 08:49:06 +0200 [thread overview]
Message-ID: <1219646946.20732.14.camel@twins> (raw)
In-Reply-To: <alpine.DEB.0.82.0808242145350.15834@skynet.skynet.ie>
On Sun, 2008-08-24 at 21:57 +0100, Dave Airlie wrote:
> > Quite frankly, I'm not going to take this.
> >
> > None of what you describe sounds like regressions, and this is just TOO
> > F*CKING LATE to take big changes like this, to a fragile subsystem that
> > has historically easily introduced new regressions.
> >
> > Can you please make a branch with ONLY REGRESSIONS, or fixes for major
> > problems that don't introduce several thousand lines of new code?
> >
> > Because you seem to be constantly unable to understand what "merge window"
> > means. And I'm not going to take this kind of crap.
>
> I thought you might say that, I'll re-send with just the ones that fix the
> major issues, instead of ones that fix issues people wanted fixed. Most of
> the real bits were in Rawhide kernels for a few weeks, which tbh kicks the
> ass outta a linux-next/linux-mm test cycle.
>
> Your reply now serves as place to point people at when they ask why Red
> Hat/Fedora ships features that they can't get for 1-6 months, and I'm fine
> with that.
6 months sounds too long, there's at least one merge window in such a
time-frame.
next prev parent reply other threads:[~2008-08-25 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 7:18 [git pull] drm patches for 2.6.27 final Dave Airlie
2008-08-24 17:16 ` Linus Torvalds
2008-08-24 20:57 ` Dave Airlie
2008-08-25 6:49 ` Peter Zijlstra [this message]
2008-08-25 7:57 ` Peter Zijlstra
2008-08-25 8:03 ` Dave Airlie
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=1219646946.20732.14.camel@twins \
--to=peterz@infradead.org \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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