All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens.net>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: Charles Duffy <charles@dyfis.net>,
	grub-devel@gnu.org, Ignat Korchagin <ignat@cloudflare.com>
Subject: Re: [PATCH REBASED] verify: search keyid in hashed signature subpackets
Date: Fri, 29 May 2020 23:11:20 +1000	[thread overview]
Message-ID: <87367i28ef.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <20200529113501.3iq72outl5yzgtnx@tomti.i.net-space.pl>

Daniel Kiper <dkiper@net-space.pl> writes:

> On Fri, May 29, 2020 at 02:10:46PM +1000, Daniel Axtens wrote:
>> Charles Duffy <charles@dyfis.net> writes:
>>
>> > Amended the test repo to apply this patch; it applies and works-as-intended
>> > on both 2.04 and current master.
>> >
>> > As for the DCO assertions, my portion of the contribution was implemented
>> > strictly on personal time/equipment, so I'm able to to make the relevant
>> > assertions in my individual capacity; amended below thusly.
>>
>> Awesome, me too.
>
> Oh, nice to see that work revived...
>
>> >> (Add further description per thread at
>> >> https://lists.gnu.org/archive/html/grub-devel/2016-11/msg00073.html)
>>
>> I will leave doing further revisions to you - looking through the thread
>> from 2016 it looks like the commit message needs more details and maybe
>> some variable names and constants need to be cleaned up etc. Now that we
>> have all the relevant Signed-off-bys, that should all be just a matter of
>> programming. My understanding is that you should maintain all three
>
> You mean that I have to wait for next version of it...

I looked back at the 2016 thread and you had some comments there about
the clarity of the code and the details in the commit message. I imagine
those comments still stand. I was just trying to be clear to Charles
that I wasn't going to take on the task of addressing those comments,
and that he should address those and respin the patch.

>
>> S-O-Bs in the commit message for future spins, but I've never been clear
>> on what order they should be in if you make further revisions.
>
> Well, it seems to me that it depends on the project and maintainers
> preference. I prefer the oldest SOB at the top. So, in this case:
>
>   Signed-off-by: Ignat Korchagin <ignat@cloudflare.com>
>   Signed-off-by: Charles Duffy <charles@dyfis.net>
>   Signed-off-by: Daniel Axtens <dja@axtens.net>

Noted.

Regards,
Daniel


      reply	other threads:[~2020-05-29 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  3:05 [PATCH REBASED] verify: search keyid in hashed signature subpackets Daniel Axtens
2020-05-29  3:44 ` Charles Duffy
2020-05-29  4:10   ` Daniel Axtens
2020-05-29 11:35     ` Daniel Kiper
2020-05-29 13:11       ` Daniel Axtens [this message]

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=87367i28ef.fsf@dja-thinkpad.axtens.net \
    --to=dja@axtens.net \
    --cc=charles@dyfis.net \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=ignat@cloudflare.com \
    /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.