From: Stephen Hemminger <shemminger@vyatta.com>
To: Li Wei <lw@cn.fujitsu.com>
Cc: Nick Alcock <nick.alcock@oracle.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] Install the bridge command under the same name we build it.
Date: Mon, 13 Aug 2012 08:04:21 -0700 [thread overview]
Message-ID: <20120813080421.3a4593a1@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <501F2311.8070708@cn.fujitsu.com>
On Mon, 06 Aug 2012 09:51:13 +0800
Li Wei <lw@cn.fujitsu.com> wrote:
> On 08/04/2012 10:36 PM, Nick Alcock wrote:
> >
> > Signed-off-by: Nick Alcock <nick.alcock@oracle.com>
> > ---
> > bridge/Makefile | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/bridge/Makefile b/bridge/Makefile
> > index 0c333bf..9a6743e 100644
> > --- a/bridge/Makefile
> > +++ b/bridge/Makefile
> > @@ -7,8 +7,8 @@ all: bridge
> > bridge: $(BROBJ) $(LIBNETLINK)
> >
> > install: all
> > - install -m 0755 br $(DESTDIR)$(SBINDIR)
> > + install -m 0755 bridge $(DESTDIR)$(SBINDIR)
> >
> > clean:
> > - rm -f $(BROBJ) br
> > + rm -f $(BROBJ) bridge
> >
>
> Hi Nick,
>
> To post a patch for iproute2, you should send it to
> Stephen Hemminger <shemminger@vyatta.com> who is the maintainer of iproute2.
>
>
> Stephen, I also noticed this problem and thought should ask you for the final
> name of the brige extension. Personally I prefer br, it is short and
> distingushable enough.
>
> Thanks.
br was already taken by X10 package on debian.
prev parent reply other threads:[~2012-08-13 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 14:36 [PATCH iproute2] Install the bridge command under the same name we build it Nick Alcock
2012-08-06 1:51 ` Li Wei
2012-08-13 15:04 ` Stephen Hemminger [this message]
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=20120813080421.3a4593a1@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=lw@cn.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=nick.alcock@oracle.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