public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: linux-next: first tree
Date: Thu, 14 Feb 2008 23:58:38 -0500	[thread overview]
Message-ID: <200802142358.39171.lenb@kernel.org> (raw)
In-Reply-To: <20080215020019.f7cb5895.sfr@canb.auug.org.au>

On Thursday 14 February 2008 10:00, Stephen Rothwell wrote:
> Hi Rafael,
> 
> On Thu, 14 Feb 2008 15:45:55 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > Perhaps you can add:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 test
> 
> I would prefer that the trees be added by the subsystem maintainers and
> they can tell me which branch represents their expectations for the next
> kernel release (in this case 2.6.26). But thanks, hopefully you will have
> prodded them along. :-)

Rafael has it right, please add the branch above.
It will include both the upcoming ACPI and suspend patches.

Note that I reserve the right to re-base it from time to time -
so when you pull it, you want to pull it onto a new branch vs. Linux
rather than onto a previous copy of itself.

thanks,
-Len

  parent reply	other threads:[~2008-02-15  4:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080215003537.8911ce35.sfr@canb.auug.org.au>
2008-02-14 14:45 ` linux-next: first tree Rafael J. Wysocki
2008-02-14 15:00   ` Stephen Rothwell
2008-02-14 15:25     ` Martin Schwidefsky
2008-02-14 21:48       ` Stephen Rothwell
2008-02-14 15:49     ` Paul Mundt
2008-02-14 21:58       ` Stephen Rothwell
2008-02-15  4:58     ` Len Brown [this message]
2008-02-15  6:19       ` Stephen Rothwell

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=200802142358.39171.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=sfr@canb.auug.org.au \
    /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