From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Ryan Hope <rmh3093@gmail.com>, Greg KH <greg@kroah.com>,
Dave Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.sf.net
Subject: Re: [git pull] drm - fixes + radeon KMS (part 2)
Date: Tue, 16 Jun 2009 13:52:06 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906161351130.16802@localhost.localdomain> (raw)
In-Reply-To: <21d7e9970906161345q6e826d18q3a197643e370156c@mail.gmail.com>
On Wed, 17 Jun 2009, Dave Airlie wrote:
>
> Linus can you pull this tree?
I hate pulling trees when I know there are _known_ bugs.
Even during the merge window. The rest of the -rc series is for fixing up
bugs, yes, but not bugs that were introduced on purpose.
Linus
next prev parent reply other threads:[~2009-06-16 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 2:08 Dave Airlie
2009-06-15 2:22 ` Greg KH
2009-06-15 2:43 ` Dave Airlie
2009-06-16 15:53 ` Ryan Hope
2009-06-16 18:20 ` Linus Torvalds
2009-06-16 20:45 ` Dave Airlie
2009-06-16 20:52 ` Linus Torvalds [this message]
2009-06-16 20:56 ` Dave Airlie
2009-06-16 21:03 ` Greg KH
2009-06-16 18:45 ` Greg KH
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=alpine.LFD.2.01.0906161351130.16802@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmh3093@gmail.com \
/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
Powered by JetHome