From: Ross Burton <ross@burtonini.com>
To: Alex Kiernan <alex.kiernan@gmail.com>
Cc: openembedded-devel@lists.openembedded.org, Alex Kiernan <alexk@zuma.ai>
Subject: Re: [oe] [meta-networking][PATCH v2] ifupdown-ng: Add recipe
Date: Tue, 4 Jan 2022 10:28:20 +0000 [thread overview]
Message-ID: <CAAnfSTvy_xKboMuVNqodt5PduOtdj+tNM+qPc84X-Z=vKtSRWw@mail.gmail.com> (raw)
In-Reply-To: <20220103163754.32439-1-alexk@zuma.ai>
On Mon, 3 Jan 2022 at 16:40, Alex Kiernan <alex.kiernan@gmail.com> wrote:
> ifupdown-ng is a network device manager that is largely compatible with
> Debian ifupdown, BusyBox ifupdown and Cumulus Networks' ifupdown2.
If this is a superior alternative, should this be merged into oe-core
as the replacement for the existing ifupdown scripts?
Ross
next prev parent reply other threads:[~2022-01-04 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:37 [meta-networking][PATCH v2] ifupdown-ng: Add recipe Alex Kiernan
2022-01-04 10:28 ` Ross Burton [this message]
2022-01-05 12:16 ` [oe] " Otavio Salvador
2022-01-05 12:51 ` Alex Kiernan
2022-01-05 16:36 ` Ross Burton
2022-01-05 16:37 ` Khem Raj
2022-01-05 19:06 ` Khem Raj
2022-01-05 20:31 ` Alex Kiernan
2022-01-05 12:14 ` Otavio Salvador
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='CAAnfSTvy_xKboMuVNqodt5PduOtdj+tNM+qPc84X-Z=vKtSRWw@mail.gmail.com' \
--to=ross@burtonini.com \
--cc=alex.kiernan@gmail.com \
--cc=alexk@zuma.ai \
--cc=openembedded-devel@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.