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