[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091014085515.f40067c1.randy.dunlap@oracle.com>
Date: Wed, 14 Oct 2009 08:55:15 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for October 14
On Wed, 14 Oct 2009 16:34:45 +1100 Stephen Rothwell wrote:
> Changes since 20091013:
>
> Undropped tree: i7core_edac
>
> My fixes tree contains a build fix for powerpc/kvm.
>
> The pci tree gained a conflict against Linus' tree.
>
> The kbuild tree gained a build failure that required me to remove
> include/asm/asm-offsets.h from my object tree.
>
> The net tree lost its build failure.
>
> The percpu tree lost its build failure.
>
> The tty tree still had a build failure for which I reverted a commit.
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ). If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one. You should use "git fetch" as mentioned in the FAQ on the wiki
> (see below).
Hi Stephen,
Where are today's .bz2 file and the .sign files?
and when did pub/kernel/people/sfr/linux-next/ disappear?
The kernel.org/kdist/finger_banner file now reports:
The latest linux-next version of the Linux kernel is: next-20091013
instead of 20091014.
---
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists