From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: linux-next: manual merge of the x86 tree
Date: Mon, 07 Jul 2008 22:28:48 -0700
Message-ID: <4872FB10.6060807@goop.org>
References: <20080708105658.1a9deedc.sfr@canb.auug.org.au>	<4872DD62.1060708@goop.org> <20080708150103.3d52c0d0.sfr@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-next-owner@vger.kernel.org>
Received: from gw.goop.org ([64.81.55.164]:33676 "EHLO mail.goop.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750888AbYGHF25 (ORCPT <rfc822;linux-next@vger.kernel.org>);
	Tue, 8 Jul 2008 01:28:57 -0400
In-Reply-To: <20080708150103.3d52c0d0.sfr@canb.auug.org.au>
Sender: linux-next-owner@vger.kernel.org
List-ID: <linux-next.vger.kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>, linux-next@vger.kernel.org, Steven Rostedt <srostedt@redhat.com>

Stephen Rothwell wrote:
> I merge a set of branches that are specially maintained for linux-next
> (see the Next/Trees file in the linux-next tree). I assume that Linus is
> probably not going to just merge in tip.get in one enormous merge ...
>   

Yes, fair enough.

    J