From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Fw: Re: Strong Crypto Support for GRUB2
Date: Sun, 20 Jul 2008 20:20:57 -0400 [thread overview]
Message-ID: <1216599657.26998.1.camel@dv> (raw)
In-Reply-To: <20080721014952.257d99d4.dn.tlp@gmx.net>
On Mon, 2008-07-21 at 01:49 +0200, Simon Peter wrote:
> Did the message below ever arrive on the list?
...
> Date: Sun, 3 Feb 2008 18:25:47 +0100
> From: Simon Peter <simon.peter@gmx.de>
> To: The development of GRUB 2 <grub-devel@gnu.org>
> Cc: Marco Gerards <mgerards@xs4all.nl>, Robert Millan <rmh@aybabtu.com>
> Subject: Re: Strong Crypto Support for GRUB2
I don't see it in the archives for February 2008:
http://lists.gnu.org/archive/html/grub-devel/2008-02/index.html
No idea why. But this message did arrive.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-21 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 23:49 Fw: Re: Strong Crypto Support for GRUB2 Simon Peter
2008-07-21 0:20 ` Pavel Roskin [this message]
2008-07-21 9:22 ` Michael Gorven
2008-07-21 13:48 ` Colin D Bennett
2008-07-21 20:38 ` Simon Peter
2008-07-22 22:12 ` Robert Millan
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=1216599657.26998.1.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox