From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: uvv.mail@gmail.com, Openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/3] systemd: Build the systemctl executable
Date: Mon, 3 Feb 2025 13:37:45 +0200 [thread overview]
Message-ID: <Z6CqiWKzMu3BEKRe@nuoska> (raw)
In-Reply-To: <CANNYZj_sU8f011m_mxXO8s0FdsUrcjdQHcB-fBDE+6wXAo9aQA@mail.gmail.com>
Hi,
On Mon, Feb 03, 2025 at 12:32:10PM +0100, Alexander Kanavin wrote:
> On Mon, 3 Feb 2025 at 12:27, Mikko Rapeli <mikko.rapeli@linaro.org> wrote:
> > So changes without justification are fine then? I'm not against this change,
> > I would just like to understand why it's needed or proposed right now. A reason
> > could be just to reduce custom patches in oe-core. That would tell me that no
> > actual usecase is currently broken, apart from ukify.py and secureboot for which
> > I've sent a patch separately and which was seen in meta-arm side testing.
>
> Yes, reducing the amount of custom code is sufficient justification in
> itself. If you need it explicitly spelled out, there you go.
I would like these to be explicitly written in commit messages. It is
hard to guess the reasons even when I'm actively following mailing lists
and irc, and even harder much later when all I have is git log and a bisect
pointing to specific commit or its cherry-pick on a stable branch.
Cheers,
-Mikko
next prev parent reply other threads:[~2025-02-03 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 20:03 [PATCH 1/3] bitbake.conf: Add conditional host tool getent uvv.mail
2025-02-02 20:03 ` [PATCH 2/3] meson.bbclass: Add an option to specify install tags uvv.mail
2025-02-02 20:03 ` [PATCH 3/3] systemd: Build the systemctl executable uvv.mail
2025-02-02 20:17 ` Patchtest results for " patchtest
2025-02-03 7:54 ` [OE-core] " Mikko Rapeli
2025-02-03 11:07 ` Alexander Kanavin
2025-02-03 11:27 ` Mikko Rapeli
2025-02-03 11:32 ` Alexander Kanavin
2025-02-03 11:37 ` Mikko Rapeli [this message]
2025-02-03 8:53 ` Ross Burton
2025-02-03 9:35 ` Alex Kiernan
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=Z6CqiWKzMu3BEKRe@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=alex.kanavin@gmail.com \
--cc=uvv.mail@gmail.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.