All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Phil Sutter <phil@nwl.cc>, Eric Garver <egarver@redhat.com>,
	Tomas Dolezal <todoleza@redhat.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Lennert Buytenhek <buytenh@gnu.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] Introduce ip-brctl shell script
Date: Wed, 30 Jan 2019 22:12:45 -0700	[thread overview]
Message-ID: <d2cd931e-5348-a427-5935-b259e047e14a@gmail.com> (raw)
In-Reply-To: <20190130115555.61868ab9@redhat.com>

On 1/30/19 3:55 AM, Stefano Brivio wrote:
>> I get your intent, but this seems more appropriate for you / Red Hat to
>> carry than something we want to distribute as part of iproute2.
> 
> Sure, I could also do that, but:
> 
> - me creating another project: similar maintenance burden for
>   distribution maintainers as keeping bridge-utils around,
>   for something that won't have any active development
> 
> - carrying it in a single distribution downstream: I would have gone
>   that way if I thought it wouldn't be useful for others. I myself use
>   (also) distributions other than Fedora/RHEL and this would feel
>   just... wrong
> 
> Why do you think it's not appropriate to distribute this as part of
> iproute2? Too ugly? Bloated? Anything I can improve?
> 
> I think it would be appropriate because it intimately depends on
> ip-link -- it's really nothing more than a helper for iproute2 tools.
> 

Again, I understand your point ... I still, too often, type ifconfig
from long in-grained muscle memory.

This is a convenience wrapper around commands packaged in iproute2. If
iproute2 adds this wrapper, it will have to carry it and maintain it
forever. Distributions (Fedora, RHEL, Debian, etc) may see it
differently and decide to add this patch onto iproute2 that they
distribute as a means for dropping bridge-utils. That's a reasonable
migration choice. It is just not something upstream iproute2 should carry.

  reply	other threads:[~2019-01-31  5:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 17:00 [PATCH iproute2-next] Introduce ip-brctl shell script Stefano Brivio
2019-01-23 15:09 ` Nikolay Aleksandrov
2019-01-23 16:33   ` Roopa Prabhu
2019-01-25 10:05     ` Stefano Brivio
2019-01-28  5:08       ` Roopa Prabhu
2019-01-28  7:57         ` Stefano Brivio
2019-01-30 22:30           ` Roopa Prabhu
2019-01-31 12:46             ` Stefano Brivio
2019-01-31 16:28               ` Roopa Prabhu
2019-02-05 22:50                 ` Stephen Hemminger
2019-02-06 10:55                   ` Stefano Brivio
2019-01-25 10:04   ` Stefano Brivio
2019-01-30  4:51 ` David Ahern
2019-01-30 10:55   ` Stefano Brivio
2019-01-31  5:12     ` David Ahern [this message]
2019-01-31 12:46       ` Stefano Brivio
2019-01-31 12:49 ` Stefano Brivio

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=d2cd931e-5348-a427-5935-b259e047e14a@gmail.com \
    --to=dsahern@gmail.com \
    --cc=buytenh@gnu.org \
    --cc=egarver@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=phil@nwl.cc \
    --cc=sbrivio@redhat.com \
    --cc=stephen@networkplumber.org \
    --cc=todoleza@redhat.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 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.