Thanks, I pushed this. Yeah, nroff syntax is unreadable. It's barely writable, in fact.
On Mon, Sep 19, 2011 at 01:37:26PM -0700, Reid Price wrote: > Text LGTM, thanks. I'm useless at grok-ing the markup, assume it is correct > =) > > On Mon, Sep 19, 2011 at 1:22 PM, Ben Pfaff <[email protected]> wrote: > > > Suggestion #7370. > > Suggested-by: Reid Price <[email protected]> > > --- > > utilities/ovs-ofctl.8.in | 7 ++++++- > > 1 files changed, 6 insertions(+), 1 deletions(-) > > > > diff --git a/utilities/ovs-ofctl.8.in b/utilities/ovs-ofctl.8.in > > index 100faf0..f2ed8a4 100644 > > --- a/utilities/ovs-ofctl.8.in > > +++ b/utilities/ovs-ofctl.8.in > > @@ -276,8 +276,13 @@ may be specified to explicitly mark any of these > > fields as a wildcard. > > (\fB*\fR should be quoted to protect it from shell expansion.) > > . > > .IP \fBin_port=\fIport_no\fR > > -Matches physical port \fIport_no\fR. Switch ports are numbered as > > +Matches OpenFlow port \fIport_no\fR. Ports are numbered as > > displayed by \fBovs\-ofctl show\fR. > > +.IP > > +(The \fBresubmit\fR action can search OpenFlow flow tables with > > +arbitrary \fBin_port\fR values, so flows that match port numbers that > > +do not exist from an OpenFlow perspective can still potentially be > > +matched.) > > . > > .IP \fBdl_vlan=\fIvlan\fR > > Matches IEEE 802.1q Virtual LAN tag \fIvlan\fR. Specify \fB0xffff\fR > > -- > > 1.7.4.4 > > > > _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
