From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: jarod@redhat.com, mkubecek@suse.cz, netdev@vger.kernel.org
Subject: Re: [RFC] bonding driver terminology change proposal
Date: Thu, 16 Jul 2020 16:01:52 -0700 [thread overview]
Message-ID: <20200716160152.026ace81@hermes.lan> (raw)
In-Reply-To: <20200716.115947.741360685940124518.davem@davemloft.net>
On Thu, 16 Jul 2020 11:59:47 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Jarod Wilson <jarod@redhat.com>
> Date: Wed, 15 Jul 2020 23:06:55 -0400
>
> > On Mon, Jul 13, 2020 at 9:00 PM David Miller <davem@davemloft.net> wrote:
> >>
> >> From: Michal Kubecek <mkubecek@suse.cz>
> >> Date: Tue, 14 Jul 2020 00:00:16 +0200
> >>
> >> > Could we, please, avoid breaking existing userspace tools and scripts?
> >>
> >> I will not let UAPI breakage, don't worry.
> >
> > Seeking some clarification here. Does the output of
> > /proc/net/bonding/<bond> fall under that umbrella as well?
>
> Yes, anything user facing must not break.
>
For iproute2, would like better wording on the command
parameters (but accept the old names so as not to break scripts).
The old names can be highlighted as for compatibility only
or removed from the usage manual and usage.
Internally, variable names and function names can change iproute2
since the internal API's are not considered part of user API.
next prev parent reply other threads:[~2020-07-16 23:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 18:51 [RFC] bonding driver terminology change proposal Jarod Wilson
2020-07-13 21:36 ` Eric Dumazet
2020-07-14 18:01 ` Jarod Wilson
2020-07-13 22:00 ` Michal Kubecek
2020-07-13 22:41 ` Stephen Hemminger
2020-07-14 0:09 ` Michal Kubecek
2020-07-14 0:26 ` Andrew Lunn
2020-07-16 3:04 ` Jarod Wilson
2020-07-16 3:18 ` Andrew Lunn
2020-07-16 5:43 ` Jarod Wilson
2020-08-13 3:42 ` Jarod Wilson
2020-07-14 0:55 ` Jay Vosburgh
2020-07-14 18:15 ` Jarod Wilson
2020-07-15 12:56 ` Edward Cree
2020-07-15 19:23 ` Jarod Wilson
2020-07-14 1:00 ` David Miller
2020-07-16 3:06 ` Jarod Wilson
2020-07-16 18:59 ` David Miller
2020-07-16 23:01 ` Stephen Hemminger [this message]
2020-07-14 18:04 ` Jarod Wilson
2020-07-14 0:51 ` David Miller
2020-07-14 19:17 ` Toke Høiland-Jørgensen
2020-07-14 20:39 ` Marcelo Ricardo Leitner
2020-07-14 21:24 ` Jarod Wilson
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=20200716160152.026ace81@hermes.lan \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=jarod@redhat.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.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 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).