From: thefly <thefly@acaro.org>
To: linux-kernel@vger.kernel.org
Subject: What was wrong with merge-mem?
Date: Mon, 24 Feb 2003 16:39:30 +0100 [thread overview]
Message-ID: <20030224153930.GA674@tyler> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Hello everybody,
i'm planning to port merge-mem to 2.4/2.5, i've started
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.
TIA
--
Claudio "thefly" Martella
thefly@acaro.org
claudio.martella@polimi.it
GNU/PG keyid: 0x8EA95625
- Powered by Debian GNU/Linux -
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-02-24 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 15:39 thefly [this message]
2003-02-24 15:56 ` What was wrong with merge-mem? Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030224153930.GA674@tyler \
--to=thefly@acaro.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.