From: Stephen Hemminger <stephen@networkplumber.org>
To: Ido Schimmel <idosch@idosch.org>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Petr Machata <petrm@nvidia.com>, David Ahern <dsahern@gmail.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Report: iproute2 build broken?
Date: Mon, 4 Jul 2022 12:07:19 -0700 [thread overview]
Message-ID: <20220704120719.505ed58e@hermes.local> (raw)
In-Reply-To: <YsMgv2plWTuWcd4X@shredder>
On Mon, 4 Jul 2022 20:17:51 +0300
Ido Schimmel <idosch@idosch.org> wrote:
> On Mon, Jul 04, 2022 at 12:59:45PM -0400, Jamal Hadi Salim wrote:
> > Thanks Ido. That fixed it.
> > General question: do we need a "stable" iproute2?
>
> Maybe a new point release is enough (e.g., 5.18.1)?
I don't think this is urgent enough for another release.
next prev parent reply other threads:[~2022-07-04 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 15:51 Report: iproute2 build broken? Jamal Hadi Salim
2022-07-04 16:04 ` Jamal Hadi Salim
2022-07-04 16:34 ` Ido Schimmel
2022-07-04 16:59 ` Jamal Hadi Salim
2022-07-04 17:17 ` Ido Schimmel
2022-07-04 19:07 ` Stephen Hemminger [this message]
2022-07-06 11:26 ` Jamal Hadi Salim
2022-07-04 17:07 ` Stephen Hemminger
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=20220704120719.505ed58e@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).