Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 24 Feb 2003 10:29:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 24 Feb 2003 10:29:18 -0500 Received: from relay-2.fastweb.it ([213.140.2.40]:59591 "EHLO mail.fastwebnet.it") by vger.kernel.org with ESMTP id ; Mon, 24 Feb 2003 10:29:17 -0500 Date: Mon, 24 Feb 2003 16:39:30 +0100 From: thefly To: linux-kernel@vger.kernel.org Subject: What was wrong with merge-mem? Message-ID: <20030224153930.GA674@tyler> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline X-Mailer: Mutt 1.5.3i (2002-12-17) X-Editor: VIM - Vi IMproved 6.1 (2002 Mar 24, compiled Feb 8 2003 12:42:35) User-Agent: Mutt/1.5.3i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1127 Lines: 40 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello everybody, i'm planning to port merge-mem to 2.4/2.5, i've started=20 designing the whole stuff, but what i miss is what was wrong with the previous attempt. I googled the past posts but could'nt find much about it, just someone who reports security problems that i don't share.=20 TIA --=20 Claudio "thefly" Martella thefly@acaro.org claudio.martella@polimi.it GNU/PG keyid: 0x8EA95625 - Powered by Debian GNU/Linux - --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+WjyyygeBqo6pViURAvUYAKDUxvbd1CvSpNPT2pPM4KtZxPHsUACglqQ1 /aDZss6AAkJNKOuHC0VX8+g= =rOjI -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- - 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/