Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Colin D Bennett <colin@gibibit.com>
Subject: Re: Strong Crypto Support for GRUB2
Date: Wed, 23 Jul 2008 00:12:43 +0200	[thread overview]
Message-ID: <20080722221243.GD15825@thorin> (raw)
In-Reply-To: <20080721223837.46c3e052.dn.tlp@gmx.net>

On Mon, Jul 21, 2008 at 10:38:37PM +0200, Simon Peter wrote:
> > > What's missing to get my code into GRUB2 mainline?
> > I think you'll have to assign copyright to the FSF.
> 
> What part of it?
> 
> I learned that Michael Gorven already replaced the problematic parts
> (RIPEMD and AES) with versions from libgcrypt.

That sounds very good.  I think it was the stumbling block last time.

I expect Marco or Okuji will contact you soon about copyright assignment.
If they haven't already, you might want to mail them a reminder.

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2008-07-22 22:13 UTC|newest]

Thread overview: 17+ 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
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-13  9:16 Simon Peter
2007-11-10 17:22 ` Marco Gerards
2007-09-02 12:17 Simon Peter
2007-09-02 16:05 ` Robert Millan
2007-09-02 17:25   ` Simon Peter
2007-09-02 19:41     ` Robert Millan
2007-09-02 20:53       ` Simon Peter
2007-09-02 23:05         ` Robert Millan
2007-09-03 18:51           ` Simon Peter
2007-11-10 17:20             ` Marco Gerards
2007-09-03  9:42       ` Patrick Georgi

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=20080722221243.GD15825@thorin \
    --to=rmh@aybabtu.com \
    --cc=colin@gibibit.com \
    --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