All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Markus Volk <f_l_k@t-online.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] Remove usage of /var/volatile/tmp
Date: Fri, 17 Mar 2023 11:53:17 +0000	[thread overview]
Message-ID: <a1807744c2e652e0d05c1c313039e697b2b07d1e.camel@linuxfoundation.org> (raw)
In-Reply-To: <9FONRR.ZLSABXKTP67E@t-online.de>

On Fri, 2023-03-17 at 09:18 +0100, Markus Volk wrote:
> Am Fr, 17. Mär 2023 um 08:00:37 +0000 schrieb Richard Purdie
> <richard.purdie@linuxfoundation.org>:
> > This changes the system layout to what systemd wants but what
> > happens
> > to sysvinit or anything else though? Some systems won't have
> > systemd-
> > tmpfiles and so on present. The commit message above makes it sound
> > like systemd is the only thing that exists/matters.
> 
> 
> I like systemd and I like that it standardizes a lot of things, but I
> really don't care about politics. That's why I also sent a patch for
> a different way. But the commit message is right, that would clearly
> be a step towards systemd.

Regardless of what anyone thinks of systemd, I can't take patches which
change existing behaviours if that change isn't explained, justified
and documented.

As such there is no way I could ever take a patch with the commit
message in the current form since it doesn't mention anything about the
impact on sysvinit, how to mitigate it (if needed) and what users
should expect.

I appreciate you likely don't care about sysvinit and don't want to
spend any time on that. That is fine, I do understand. Equally, as the
maintainer for OE-Core, I do have to care and I just can't take a patch
like this. I just want to make it clear why it isn't something I can
even consider in the current form and to make any change like this,
we'd need more insight into the other impacts (e.g. busybox init too).

It would help me if adverse effects are mentioned in commit messages.
In this case I can spot it easily enough but I don't always know/spot
all the issues.

Cheers,

Richard


  reply	other threads:[~2023-03-17 11:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  6:02 [oe-core][PATCH] Remove usage of /var/volatile/tmp Markus Volk
2023-03-17  6:04 ` Markus Volk
2023-03-17  7:34 ` Alexander Kanavin
2023-03-17  8:00 ` Richard Purdie
2023-03-17  8:18   ` Markus Volk
2023-03-17 11:53     ` Richard Purdie [this message]
2023-03-17 17:31       ` Markus Volk
2023-03-17 19:10         ` Alexander Kanavin
2023-03-22 19:00           ` f_l_k
2023-03-22 19:11             ` Alexander Kanavin
     [not found]               ` <9VVZRR.NLXPW4ISUM5R2@t-online.de>
2023-03-23 22:34                 ` Richard Purdie
2023-03-24 17:34               ` Markus Volk
2023-03-24 19:53                 ` Alexander Kanavin
2023-03-24 23:13                   ` Markus Volk
2023-03-25 18:38                     ` Alexander Kanavin
2023-03-25 19:19                       ` Markus Volk
     [not found]               ` <174F6B63D17BDF87.25304@lists.openembedded.org>
2023-03-24 17:58                 ` Markus Volk

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=a1807744c2e652e0d05c1c313039e697b2b07d1e.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=f_l_k@t-online.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.