linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [git tree] drm tree for 2.6.16-rc1
Date: Thu, 12 Jan 2006 10:17:52 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601121016020.3535@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0601120948270.1552@skynet>



On Thu, 12 Jan 2006, Dave Airlie wrote:
> 
> Hi Linus,
> 	Can you pull the drm-forlinus branch from
> git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git
> 
> This is a pretty major merge over of DRM CVS, and every driver in the DRM
> is brought up to latest versions....

I'm actually somewhat inclined to not pull any more. We've had lots of 
(hopefully minor) issues for the last few days, and I know that people 
had DRM issues with the -mm tree (which I assume tracked this tree) not 
more than a week or so ago.

IOW, I want to make sure that my tree is somewhat stable again. I don't 
want -rc1 to be horrible.

		Linus

  reply	other threads:[~2006-01-12 18:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  9:52 [git tree] drm tree for 2.6.16-rc1 Dave Airlie
2006-01-12 18:17 ` Linus Torvalds [this message]
2006-01-12 20:33   ` Dave Airlie
2006-01-12 21:52     ` Linus Torvalds
2006-01-12 21:42   ` git status (was: drm tree for 2.6.16-rc1) Andrew Morton
2006-01-12 21:55     ` Dominik Brodowski
2006-01-12 21:55     ` David Woodhouse
2006-01-12 22:07       ` Andrew Morton
2006-01-12 22:57         ` David Woodhouse
2006-01-12 22:07     ` git status Roland Dreier
2006-01-12 22:11     ` git status (was: drm tree for 2.6.16-rc1) Dmitry Torokhov
2006-01-15  9:55     ` Wim Van Sebroeck
2006-01-12 22:55   ` Stuff left for 2.6.16-rc1 (was: [git tree] " Russell King

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=Pine.LNX.4.64.0601121016020.3535@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).