From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Cryptography
Date: Tue, 17 Nov 2009 13:56:26 +0100 [thread overview]
Message-ID: <20091117125626.GA12325@thorin> (raw)
In-Reply-To: <20091117122107.GA11991@thorin>
On Tue, Nov 17, 2009 at 01:21:07PM +0100, Robert Millan wrote:
> On Mon, Nov 16, 2009 at 02:48:02PM +0100, Vladimir 'phcoder' Serbinenko wrote:
> > === added file 'include/grub/cipher_wrap.h'
> > --- include/grub/cipher_wrap.h 1970-01-01 00:00:00 +0000
> > +++ include/grub/cipher_wrap.h 2009-11-13 16:51:09 +0000
>
> Can we avoid cluttering the grub/ namespace with glue code?
Sorry, what I said is confusing. I didn't mean the grub/ namespace, I mean
the "default" namespace (in which grub/* is included but also multiboot.h).
lib-linux has its own namespace where we put things like linux/* and asm/*,
I think a similar approach would be desireable for consistency.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-11-17 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 13:48 [PATCH] Cryptography Vladimir 'phcoder' Serbinenko
2009-11-16 14:35 ` Robert Millan
2009-11-16 14:56 ` Vladimir 'phcoder' Serbinenko
2009-11-16 18:26 ` Robert Millan
2009-11-16 19:38 ` Vladimir 'phcoder' Serbinenko
2009-11-16 19:59 ` Robert Millan
2009-11-16 20:20 ` Vladimir 'phcoder' Serbinenko
2009-11-16 21:16 ` Import of libgcrypt 1.4.4 ciphers (was: Re: [PATCH] Cryptography) Robert Millan
2009-11-16 14:42 ` [PATCH] Cryptography Felix Zielcke
2009-11-16 14:58 ` Vladimir 'phcoder' Serbinenko
2009-11-17 12:21 ` Robert Millan
2009-11-17 12:56 ` Robert Millan [this message]
2009-12-05 15:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20091117125626.GA12325@thorin \
--to=rmh@aybabtu.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 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.