All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch
Date: Fri, 21 Feb 2025 09:12:10 +0000	[thread overview]
Message-ID: <49dec7e116d95938712d10e4d76b78ed2df01ca9.camel@linuxfoundation.org> (raw)
In-Reply-To: <TYWPR01MB11861B276559403A8AA76A8EFDCC72@TYWPR01MB11861.jpnprd01.prod.outlook.com>

On Fri, 2025-02-21 at 08:27 +0000, wangmy via lists.yoctoproject.org wrote:
> It's definitely the best thing to be able to do this
> 
> But there are many patches with this problem, and it is uncertain
> what the purpose of the patch was at that time (many patches do not
> have commit information).
> In addition, most upstream have not been maintained or updated for a
> long time, so the feasibility of modifying them all seems not very
> high.
> 
> It is best for the author of the patch to make the modifications.

That layer is struggling for maintainer time and the authors of the
patches have moved on to other things a long time ago. I therefore
don't think it will happen by the author or the layer maintainer.

We do really need to work out that information but it isn't an easy
job. This is why we now require it but these patches date from before
we did that. It will need someone to spend time on it.
Cheers,

Richard


  reply	other threads:[~2025-02-21  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21  3:26 [yocto-patches] [meta-java] QA Issue: Missing Upstream-Status in patch Mingyu Wang (Fujitsu)
2025-02-21  3:40 ` Khem Raj
2025-02-21  8:27   ` Mingyu Wang (Fujitsu)
2025-02-21  9:12     ` Richard Purdie [this message]
2025-02-21  9:20       ` Alexander Kanavin
2025-02-25  0:07         ` FW: " Mingyu Wang (Fujitsu)
2025-02-25  0:21         ` Mingyu Wang (Fujitsu)
2025-02-25  7:55           ` Alexander Kanavin
2025-02-26  0:34             ` Mingyu Wang (Fujitsu)
2025-02-26 10:03               ` Alexander Kanavin
2025-02-26 11:35                 ` Richard Purdie

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=49dec7e116d95938712d10e4d76b78ed2df01ca9.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=yocto-patches@lists.yoctoproject.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.