Hi Andi, On Sun, 06 Jul 2008 20:48:49 +0200 Andi Kleen <andi@xxxxxxxxxxxxxx> 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? > (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 not quite yet the full state intended for the merge, a few > patches are still missing. So what is missing, and why should we merge stuff in 2.6.27 that we don't see until the merge window? (Not trying to be antagonistic, just asking about procedure and wondering why stuff for 2.6.27 is still not in linux-next.) -- Cheers, Stephen Rothwell sfr@xxxxxxxxxxxxxxxx http://www.canb.auug.org.au/~sfr/
Attachment:
pgpAPv56Rso6P.pgp
Description: PGP signature
