From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: error from make on luks branch
Date: Thu, 11 Aug 2011 14:39:53 +0200 [thread overview]
Message-ID: <4E43CD99.60607@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1108101541140.11998@shell.eskimo.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On 11.08.2011 01:01, Charles A. Hewson wrote:
> Hi all,
> Today I did bzr checkout, configure & make. GRUB_CRYPTODISK_ENABLE=y
> was set and exported. Did I miss some dependency? Will this work on
> 32-bit machine? I am new to bzr. Is something required besides
> checkout? What additional information can I provide? Charles
Luks branch isn't used anymore. What was in it is already merged into
mainline
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-08-11 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 23:01 error from make on luks branch Charles A. Hewson
2011-08-11 12:39 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-08-11 12:43 ` Craig Sparks
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=4E43CD99.60607@gmail.com \
--to=phcoder@gmail.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.