From: Adrian Bunk <bunk@stusta.de>
To: openembedded-core@lists.openembedded.org
Subject: Should patchtest warn on Upstream-Status: Pending ?
Date: Sun, 15 Dec 2019 20:37:56 +0200 [thread overview]
Message-ID: <20191215183756.GB14038@localhost> (raw)
I am wondering whether patchtest should send warning emails on
Upstream-Status: Pending
In practice patches are usually forwarded upstream either at submission
or never.[1]
Not upstreamed OE-only patches create a technical debt that often makes
recipe upgrades a pain.
cu
Adrian
[1] When upstream requires copyright assignment upstreaming
later is sometimes not even legally possible.
next reply other threads:[~2019-12-15 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 18:37 Adrian Bunk [this message]
2019-12-15 19:16 ` Should patchtest warn on Upstream-Status: Pending ? Alexander Kanavin
2019-12-16 11:26 ` Ross Burton
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=20191215183756.GB14038@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.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.