From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Alexander Kanavin <alex.kanavin@gmail.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>,
Ross Burton <Ross.Burton@arm.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/3] insane: Improve patch warning/error handling
Date: Mon, 23 Jan 2023 10:08:14 +0200 [thread overview]
Message-ID: <Y85AbhShAXaXZP4U@nuoska> (raw)
In-Reply-To: <1cfa5fc2c0edda2cd9990de4839d130e3f7b5be9.camel@linuxfoundation.org>
Hi,
On Sun, Jan 22, 2023 at 10:19:29PM +0000, Richard Purdie wrote:
> I was hoping something simpler would suffice. I don't think I have a
> lot of interest in going beyond this, particularly given the likely
> impacts, both code wise and socially. If people don't want to do this I
> am really running low on the energy to try and push it forward. Making
> changes is hard, the socialising acceptance of a patch is the piece
> many people overlook and it isn't here in this case.
I'm requesting Upstream-Status to be filled to every patch file in
reviews. There is a lot of value in this information when maintaining
layers for a longer time. I want this. Everyone I speak with understands
how important this information is and that it's better to figure things
out or at least trigger discussion with upstream projects before
accepting patches.
-Mikko
next prev parent reply other threads:[~2023-01-23 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 14:22 [PATCH 1/3] insane: Improve patch warning/error handling Richard Purdie
2023-01-18 14:22 ` [PATCH 2/3] pseudo: Update to pull in linux-libc-headers race fix Richard Purdie
2023-01-18 14:22 ` [PATCH 3/3] pseudo: Switch back to the master branch Richard Purdie
2023-01-18 16:46 ` [OE-core] " Luca Ceresoli
2023-01-18 17:04 ` Richard Purdie
2023-01-19 9:24 ` [OE-core] [PATCH 1/3] insane: Improve patch warning/error handling Luca Ceresoli
2023-01-19 9:57 ` Richard Purdie
2023-01-19 13:55 ` Bruce Ashfield
2023-01-19 14:40 ` Richard Purdie
2023-01-19 14:52 ` Bruce Ashfield
2023-01-19 14:55 ` Richard Purdie
2023-01-19 14:56 ` Ross Burton
2023-01-20 14:26 ` Bruce Ashfield
2023-01-20 19:10 ` Alexander Kanavin
2023-01-20 19:29 ` Bruce Ashfield
2023-01-20 19:38 ` Alexander Kanavin
2023-01-20 23:00 ` Richard Purdie
2023-01-22 12:46 ` Peter Kjellerstedt
2023-01-22 22:19 ` Richard Purdie
2023-01-23 8:08 ` Mikko Rapeli [this message]
2023-01-23 9:18 ` Alexander Kanavin
[not found] ` <173BAB83B1A056B8.24231@lists.openembedded.org>
2023-01-19 9:52 ` Luca Ceresoli
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=Y85AbhShAXaXZP4U@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=Ross.Burton@arm.com \
--cc=alex.kanavin@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=richard.purdie@linuxfoundation.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.