From: Mike Crowe <mac@mcrowe.com>
To: Yoann Congal <yoann.congal@smile.fr>,
Alex Kiernan <alex.kiernan@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [scarthgap][PATCH] dropbear: Disable DSS correctly
Date: Fri, 10 Jul 2026 10:07:42 +0100 [thread overview]
Message-ID: <alC2XjkPiCD1RpJV@mcrowe.com> (raw)
In-Reply-To: <DJUPP65UURBF.TY8K27J2AQTP@smile.fr>
On Friday 10 July 2026 at 09:27:39 +0200, Yoann Congal wrote:
> On Thu Jul 9, 2026 at 9:33 PM CEST, Alex Kiernan wrote:
> > On Thu, Jul 9, 2026 at 8:07 PM Mike Crowe via lists.openembedded.org
> > <mac=mcrowe.com@lists.openembedded.org> wrote:
> >> I wasn't aware that I was expected to add one to the patch itself for a
> >> backport.
> >>
> >> https://docs.yoctoproject.org/scarthgap/contributor-guide/recipe-style-guide.html
> >> doesn't seem to say that a SoB should be added to the patch. It does say:
> >>
> >> | Of course, if another person later takes care of submitting this patch
> >> | upstream, the status should be changed to Submitted [where], and an
> >> | additional Signed-off-by: line should be added to the patch by the person
> >> | claiming responsibility for upstreaming.
> >>
> >> which sort of implies that a SoB should be added for original patches that
> >> are suitable for upstreaming but this patch is a backport which originated
> >> upstream (without a SoB) which isn't the same thing.
> >>
> >> Adding a SoB to an unmodified upstream backport patch feels like
> >> appropriation on my part, but I can do so if that's the policy.
> > You're certifying that the patch you're submitting is appropriately
> > licensed; it says nothing about who authored it.
> I agree with Alex: As the one requesting the backport, you are the one
> signing-off on this particular operation. The original author had
> nothing to do with that.
I thought that I did that with the signed-off-by in the openembedded-core
commit message.
> I created a bug to request clarification in the doc on this point:
> 16356 – Clarify trailers usage (Signed-off-by, ...) in imported patches
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=16356
Thanks. It feels like this needs an equivalent of
oe.qa.check_upstream_status(). Such a check would currently fail since
there are lots of existing patches that lack signed-off-bys and adding them
would be significant work because each one would need to be manually
checked. :( I suppose the check could also allow "Not-signed-off-by:
<openembedded-core@lists.openembedded.org>" or similar as a workaround for
existing patches with a plan to eventually remove it as the patches are
updated.
v2 sent with signed-off-by in the patch.
Thanks.
Mike.
next prev parent reply other threads:[~2026-07-10 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 16:50 [scarthgap][PATCH] dropbear: Disable DSS correctly mac
2026-07-07 8:54 ` [OE-core] " Yoann Congal
2026-07-09 19:07 ` Mike Crowe
2026-07-09 19:33 ` Alex Kiernan
2026-07-10 7:27 ` Yoann Congal
2026-07-10 9:07 ` Mike Crowe [this message]
2026-07-10 9:18 ` Yoann Congal
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=alC2XjkPiCD1RpJV@mcrowe.com \
--to=mac@mcrowe.com \
--cc=alex.kiernan@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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.