From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andi Kleen <andi@firstfloor•org>
Cc: linux-acpi@vger•kernel.org, akpm@osdl•org, linux-next@vger•kernel.org
Subject: Re: ACPI git trees and vacation
Date: Mon, 7 Jul 2008 10:03:56 +1000 [thread overview]
Message-ID: <20080707100356.fddcce73.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080707095659.a1b486e1.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Hi Andi,
On Mon, 7 Jul 2008 09:56:59 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> On Sun, 06 Jul 2008 20:48:49 +0200 Andi Kleen <andi@firstfloor•org> wrote:
> >
> > The trees for the next ACPI merge are at git.kernel.org now
> > These are based on Len's branches with some additional patches.
> >
> > (based on Linus' tree aka 2.6.26rc9)
> > git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-acpi-2.6.git release
> > Intended for the 2.6.27 merge
>
> If that is true ..
>
> > git://git.kernel.org/pub/scm/git/linux/kernel/ak/linux-acpi-2.6.git test
>
> Then why is linux-next tracking that?
So maybe I read that wrong. It appears that the release branch is
already a subset Linus' tree and you meant that comment ("Intended for
the 2.6.27 merge") was meant to apply to the test branch. Right?
> > (based on Linux next for patches with dependencies)
> > git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-next-acpi.git
>
> Is there something we can do about those dependencies?
This is still a valid question as I have been trying to push trivial
dependencies into Linus' tree ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-07 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 18:48 ACPI git trees and vacation Andi Kleen
2008-07-06 23:56 ` Stephen Rothwell
2008-07-07 0:03 ` Stephen Rothwell [this message]
2008-07-07 6:17 ` Andi Kleen
2008-07-07 6:45 ` 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=20080707100356.fddcce73.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@osdl$(echo .)org \
--cc=andi@firstfloor$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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