From: Date Huang <tjjh89017@hotmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: roopa@nvidia.com, razor@blackwall.org, jiri@resnulli.us,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [PATCH iproute2-next v2 2/2] bridge: vlan: fix compressvlans usage
Date: Mon, 25 Mar 2024 13:34:13 +0800 [thread overview]
Message-ID: <MAZP287MB0503E04A5039E47B073C8E2FE4362@MAZP287MB0503.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20240322084145.3e081475@hermes.local>
Hi Stephen
On 3/22/2024 11:41 PM, Stephen Hemminger wrote:
> On Fri, 22 Mar 2024 20:39:23 +0800
> Date Huang <tjjh89017@hotmail.com> wrote:
>
>> diff --git a/man/man8/bridge.8 b/man/man8/bridge.8
>> index eeea4073..bb02bd27 100644
>> --- a/man/man8/bridge.8
>> +++ b/man/man8/bridge.8
>> @@ -22,6 +22,7 @@ bridge \- show / manipulate bridge addresses and devices
>> \fB\-s\fR[\fItatistics\fR] |
>> \fB\-n\fR[\fIetns\fR] name |
>> \fB\-b\fR[\fIatch\fR] filename |
>> +\fB\-com\fR[\fIpressvlans\fR] |
>> \fB\-c\fR[\fIolor\fR] |
>> \fB\-p\fR[\fIretty\fR] |
>> \fB\-j\fR[\fIson\fR] |
>> @@ -345,6 +346,11 @@ Don't terminate bridge command on errors in batch mode.
>> If there were any errors during execution of the commands, the application
>> return code will be non zero.
>>
>> +.TP
>> +.BR "\-com", " \-compressvlans"
>> +Show compressed VLAN list. It will show continuous VLANs with the range instead
>> +of separated VLANs. Default is off.
>> +
>
> Overlapping option strings can cause problems, maybe a better word?
I just add the missing manual page and change the usage for the current
implementation. Maybe you could suggest some better option string for us?
Thank you
Date
prev parent reply other threads:[~2024-03-25 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240322123923.16346-1-tjjh89017@hotmail.com>
2024-03-22 12:39 ` [PATCH iproute2-next v2 1/2] bridge: vlan: fix compressvlans usage Date Huang
2024-03-22 12:54 ` Nikolay Aleksandrov
2024-03-22 12:39 ` [PATCH iproute2-next v2 2/2] " Date Huang
2024-03-22 12:54 ` Nikolay Aleksandrov
2024-03-22 15:41 ` Stephen Hemminger
2024-03-25 5:34 ` Date Huang [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=MAZP287MB0503E04A5039E47B073C8E2FE4362@MAZP287MB0503.INDP287.PROD.OUTLOOK.COM \
--to=tjjh89017@hotmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=stephen@networkplumber.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 read-only IMAP folder(s) and NNTP newsgroup(s).