All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Washburn <development@efficientek.com>
To: Forest <forestix@nom.one>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH v2] cryptodisk: allow the user to retry failed passphrases
Date: Sat, 27 Apr 2024 03:33:18 -0500	[thread overview]
Message-ID: <20240427033318.1ed48e1c@crass-HP-ZBook-15-G2> (raw)
In-Reply-To: <lu6d2jdffiuksomjl4ki3vohur85d55pfc@sonic.net>

On Mon, 22 Apr 2024 10:45:29 -0700
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.

Asking about the status of the patch in a reply to the thread can help
ensure its not overlooked. Patches do get overlooked here and if the
author is not active in pursuing the patch, there's a good chance it
will be overlooked. The development cadence might be described as
glacial, but it also depends on various factors. In your case, I
suspect one factor is that I suspect Daniel is waiting for me to review
this v2. I tend to look at patches related to cryptomount. However, I
don't have the bandwidth to check in on the list more than a few times
a month and sometimes less. So yeah, glacial.

You shouldn't have to start all over, but yes you might need to rebase
on upcoming changes depending on when this gets in.

Glenn

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

  parent reply	other threads:[~2024-04-27  8:33 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
2024-04-27  8:33   ` Glenn Washburn [this message]
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=20240427033318.1ed48e1c@crass-HP-ZBook-15-G2 \
    --to=development@efficientek.com \
    --cc=forestix@nom.one \
    --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.