From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>,
David Trudgian <dave@trudgian.net>
Cc: 38826@debbugs.gnu.org
Subject: [bug#38826] doc: Mention no LUKS2 for luks-device-mapping
Date: Thu, 02 Jan 2020 23:53:42 +0100 [thread overview]
Message-ID: <87png18o7d.fsf@nckx> (raw)
In-Reply-To: <20200102233256.4250ec30@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Danny, David,
Danny Milosavljevic 写道：
> David Trudgian <dave@trudgian.net> wrote:
>> A mention LUKS2 is not supported in the docs might be nice.
>
> I agree.
Same. Would you consider submitting a patch, David? Or writing
the text?
> But better yet would be to implement LUKS2 in the uuid code.
Has LUKS2 support[0] been added to GRUB yet? Last I checked it
hadn't.
Which isn't to say that we shouldn't get our own house in order,
of course.
Kind regards,
T G-R
[0]:
https://lists.gnu.org/archive/html/grub-devel/2019-11/msg00000.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-01-02 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 3:47 [bug#38826] doc: Mention no LUKS2 for luks-device-mapping David Trudgian
2020-01-02 22:32 ` Danny Milosavljevic
2020-01-02 22:53 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-01-03 1:56 ` David Trudgian
2020-01-10 15:39 ` [bug#38826] Fwd: [bug #55093] Add LUKS2 support Tobias Geerinckx-Rice via Guix-patches via
2020-01-10 19:03 ` David Trudgian
[not found] <20181125-133249.sv131345.66349@savannah.gnu.org>
[not found] ` <20190329-085821.sv141454.39342@savannah.gnu.org>
[not found] ` <20190529-204303.sv92573.55917@savannah.gnu.org>
[not found] ` <20191104-210711.sv164522.57380@savannah.gnu.org>
[not found] ` <20191104-214103.sv131345.42463@savannah.gnu.org>
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87png18o7d.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=38826@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=dave@trudgian.net \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).