linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-acpi@vger.kernel.org
Subject: Re: [GIT PATCH] ACPI patches for 2.6.20-rc1
Date: Fri, 22 Dec 2006 21:34:13 -0500	[thread overview]
Message-ID: <200612222134.14054.lenb@kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612202357110.3576@woody.osdl.org>

On Thursday 21 December 2006 02:58, Linus Torvalds wrote:
> 
> On Wed, 20 Dec 2006, Len Brown wrote:
> > 
> > please pull from: 
> 
> Is this really all obvious bug-fixes? There seems to be a lot of 
> development there that simply isn't appropriate after an -rc1 any more.
> 
> I want 2.6.20 to be stable, and one of the things I'm doing is to be 
> strict about the merge window.

Yes, I recommend pulling this tree now.
While there is a fair amount of text changed, the functional changes
here are actually quite small, and have been in -mm for a long time --
some of them already shipping in distros before being upstream.

Yes, there is a fair amount of fluffy cleanup here -- seems there is
never a good time in the release cycle to do them, but as andrew says,
we're in this for the long term, so we do have to do them some time.
I don't see any big risks in them so it seems appropriate to push after rc1.

Note that there is a much larger body of ACPI changes in flight
that I have excluded from this pull request and are waiting for 2.6.21.

thanks,
-Len

      reply	other threads:[~2006-12-23  2:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20  9:34 [GIT PATCH] ACPI patches for 2.6.20-rc1 Len Brown
2006-12-21  7:58 ` Linus Torvalds
2006-12-23  2:34   ` Len Brown [this message]

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=200612222134.14054.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).