To: linux-kernel@vger.kernel.org
Path: not-for-mail
From: Matthias Urlichs <smurf@smurf.noris.de>
Newsgroups: smurf.list.linux.kernel
Subject: Re: 2.6.0-rc1-mm1
Date: Sun, 04 Jan 2004 22:17:33 +0100
Organization: {M:U} IT Consulting
Message-ID: <pan.2004.01.04.21.17.28.696467@smurf.noris.de>
References: <20031231004725.535a89e4.akpm@osdl.org>
NNTP-Posting-Host: linux.smurf.noris.de
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
NNTP-Posting-Date: Sun, 4 Jan 2004 21:17:33 +0000 (UTC)
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1318
Lines: 27

Hi, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-rc1/2.6.0-rc1-mm1/

Again, available via Bitkeeper at <bk://smurf.bkbits.net/linux-2.6-mm>.

If you use this tree, please consider dropping me a note or whatever;
I don't like to work in a vacuum...

The way I've built this, in case anybody's curious:
- undo all the changes in 2.6.0-mm2 but not in 2.6.1-rc1-mm1.
- merge with 2.6.1-rc1, resolved nine conflicts.
- Apply all patches in 2.6.1-rc1-mm2 but not in 2.6.0-mm2.
  Some didn't apply fully, for whatever reason.
- Generate a diff between 2.6.1-rc1 and top-of-tree.
  Use interdiff -p1 to compare that to Andrew's official patch.
  (There were none, which was somewhat surprising.)

Oh yes, I've stopped prefixing the patch tags with mm[12]; that would get
too confusing in the long run.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Hope is a good breakfast, but it is a bad supper.
		-- Francis Bacon

-
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/