All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Plenefisch <simonpatp@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: development@efficientek.com
Subject: Re: [PATCH v2] cryptodisk: allow the user to retry failed passphrases
Date: Mon, 22 Apr 2024 14:34:54 -0400	[thread overview]
Message-ID: <CAOCpoWdHRQ0iYvKati-sP6+HFHgu5qe2bXLjhxMQm2Qc-FdZuA@mail.gmail.com> (raw)
In-Reply-To: <lu6d2jdffiuksomjl4ki3vohur85d55pfc@sonic.net>


[-- Attachment #1.1: Type: text/plain, Size: 808 bytes --]

On Mon, Apr 22, 2024 at 1:48 PM Forest <forestix@nom.one> wrote:

> On Sun, 07 Apr 2024 14:52:32 -0700, Forest wrote:
>
> >Changes since last rev:
> >- replace some spaces with tabs
> >- better explain the clearing of grub_errno
> >- let an environment variable override the number of passphrase tries
>
> As a new contributor, is there something I should do to ensure my patch
> isn't overlooked?  I'm not sure what the development cadence here is like,
> and since new patches to the same code have arrived in the weeks since I
> submitted this one, I'm starting to worry that I might have to start all
> over again on a new code base.
>
>
As another new contributor, I'm also curious about this. I've been waiting
since january & febuary, for any update on my patch, though

Patrick

[-- Attachment #1.2: Type: text/html, Size: 1160 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

  reply	other threads:[~2024-04-22 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07 21:52 [PATCH v2] cryptodisk: allow the user to retry failed passphrases Forest
2024-04-22 17:45 ` Forest
2024-04-22 18:34   ` Patrick Plenefisch [this message]
2024-04-27  8:33   ` Glenn Washburn
2024-04-27  9:18 ` Glenn Washburn
2024-04-28  0:10   ` Forest

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=CAOCpoWdHRQ0iYvKati-sP6+HFHgu5qe2bXLjhxMQm2Qc-FdZuA@mail.gmail.com \
    --to=simonpatp@gmail.com \
    --cc=development@efficientek.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.