From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Mark M. Hoffman" <mhoffman@lightlink.com>
Subject: Re: how about bringing Documentation/feature-removal-schedule.txt up to date?
Date: Tue, 17 Jul 2007 09:55:04 +0200 [thread overview]
Message-ID: <469C75D8.4000809@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070717083432.5463e8d4@hyperion.delvare>
Jean Delvare wrote:
> This one took more time than expected,
These words sound strangely familiar, as if I often said them myself.
Can't be.
--
Stefan Richter
-=====-=-=== -=== =---=
http://arcgraph.de/sr/
prev parent reply other threads:[~2007-07-17 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 12:02 how about bringing Documentation/feature-removal-schedule.txt up to date? Robert P. J. Day
2007-07-16 19:44 ` Stefan Richter
2007-07-16 19:54 ` Stefan Richter
[not found] ` <20070717083432.5463e8d4@hyperion.delvare>
2007-07-17 7:55 ` Stefan Richter [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=469C75D8.4000809@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhoffman@lightlink.com \
--cc=rpjday@mindspring.com \
/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.