Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jeroen Hofstee <oe@myspectrum.nl>
To: yoann.congal@smile.fr, alex.kanavin@gmail.com
Cc: richard.purdie@linuxfoundation.org,
	Jeroen Hofstee <jeroen@myspectrum.nl>,
	openembedded-core@lists.openembedded.org,
	Jeroen Hofstee <jhofstee@victronenergy.com>
Subject: Re: [OE-core] [PATCH] udev-extraconf: fix ifupdown for non hotplug devices
Date: Thu, 10 Apr 2025 20:32:55 +0200	[thread overview]
Message-ID: <8eee9b46-7e9a-4c1d-8daa-4e58a135d9eb@myspectrum.nl> (raw)
In-Reply-To: <CAMSfU+4QKpU=2YaO8L03R+aBzByUq=x3h-sn8yy3rRCxX==YmQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

Hello Alex and Yoann,

On 4/10/25 14:17, Yoann Congal via lists.openembedded.org wrote:
> Le jeu. 10 avr. 2025 à 12:14, Alexander Kanavin via 
> lists.openembedded.org <http://lists.openembedded.org> 
> <alex.kanavin=gmail.com@lists.openembedded.org> a écrit :
>
>     On Wed, 9 Apr 2025 at 12:40, Jeroen Hofstee via
>     lists.openembedded.org <http://lists.openembedded.org>
>     <oe=myspectrum.nl@lists.openembedded.org> wrote:
>     > For completeness, this is not some theoretical issue, always
>     calling if up
>     > directly after a network device is discovered does cause issues
>     and is
>     > against spec as well.
>     >
>     > The sed stuff isn't that complicated, is it?
>
>     I beg to differ. The code is basically unreadable (unless you want to
>     write an elaborate comment with example input->output transformations
>     for every single line it), and that in itself is reason not to take
>     it. Any software solution must not only solve the problem, it must
>     also be written such that other humans can understand and change it.
>
>     I think I'd prefer a patch to busybox; even if upstream rejects or
>     ignores it, we still have something that is easier to take care of.
>
>
> FWIW, I agree with Alexander here.
> A patch (even a local one) will be easier to maintain in the long run.
>
Cool, let me know when these patches have landed.

Regards,
Jeroen

[-- Attachment #2: Type: text/html, Size: 3153 bytes --]

  reply	other threads:[~2025-04-10 18:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 17:49 [OE-core] [PATCH] udev-extraconf: fix ifupdown for non hotplug devices Jeroen Hofstee
2025-04-09  8:37 ` Richard Purdie
2025-04-09  9:08   ` Jeroen Hofstee
2025-04-09  9:27     ` Richard Purdie
2025-04-09 10:40       ` Jeroen Hofstee
2025-04-09 10:52         ` Richard Purdie
2025-04-10 10:14         ` Alexander Kanavin
2025-04-10 12:17           ` Yoann Congal
2025-04-10 18:32             ` Jeroen Hofstee [this message]
2025-04-10 19:05               ` Alexander Kanavin
2025-04-09  9:28   ` Mike Looijmans

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=8eee9b46-7e9a-4c1d-8daa-4e58a135d9eb@myspectrum.nl \
    --to=oe@myspectrum.nl \
    --cc=alex.kanavin@gmail.com \
    --cc=jeroen@myspectrum.nl \
    --cc=jhofstee@victronenergy.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yoann.congal@smile.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox