From: jbradford@dial.pipex.com
To: m.c.p@wolk-project.de (Marc-Christian Petersen)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] [PATCH] Linux-2.5.40-mcp2
Date: Thu, 3 Oct 2002 16:29:11 +0100 (BST) [thread overview]
Message-ID: <200210031529.g93FTBED000192@darkstar.example.net> (raw)
In-Reply-To: <200210011428.49663.m.c.p@wolk-project.de> from "Marc-Christian Petersen" at Oct 03, 2002 01:42:23 PM
> first: anything that _should_ be merged into 2.5 devel tree and is
> _not_ merged so far for some good reason (f.e. needs testing,
> further development, etc.), please send me those patches and I'll
> integrate them into the -mcp tree! :) ... (if not already done)
> .. thnx!
>
> Is there really an interrest in this tree?
Yes, it is only lack of time that stops me testing it.
John.
prev parent reply other threads:[~2002-10-03 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 12:29 [ANNOUNCE] [PATCH] Linux-2.5.40-mcp1 Marc-Christian Petersen
2002-10-03 15:29 ` jbradford [this message]
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=200210031529.g93FTBED000192@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).