Message-ID: <47BBDB6E.5040109@suse.de>
Date: Wed, 20 Feb 2008 08:49:02 +0100
From: Frank Seidel <fseidel@suse.de>
Organization: SUSE LINUX Products GmbH
User-Agent: Thunderbird 2.0.0.9 (X11/20071114)
MIME-Version: 1.0
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, linux-next@vger.kernel.org,
       LKML <linux-kernel@vger.kernel.org>, linux-arch@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 20
References: <20080220163457.79b9189f.sfr@canb.auug.org.au>	<20080220055055.GC31832@kroah.com> <20080220175756.ab1ada1d.sfr@canb.auug.org.au>
In-Reply-To: <20080220175756.ab1ada1d.sfr@canb.auug.org.au>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 763
Lines: 18

Stephen Rothwell wrote:
> That would work.  Chris has the right idea, though.  Just set up
> linux-next as a remote on any existing clone of Linus' tree and the
> "fetch" will forcibly update the linux-next/master branch (remember to
> not have that branch checked out when you fetch).
> 
> If you keep a continuing git tree for this, you will have the history of
> all the next trees because I tag each one.

Thanks for that hint. Added it to the FAQ on the Wiki
(http://linux.f-seidel.de/linux-next/pmwiki/).

Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/