You're right. Thanks, I fixed that and pushed.
On Fri, Jan 13, 2012 at 03:30:40PM -0800, Ansis Atteka wrote:
> Looks, good but given example expands to "other-config=0=x
> other-config=1=y" instead of "other-config=0=x other-config=0=y" , right?
>
>
> On Fri, Jan 13, 2012 at 3:10 PM, Ben Pfaff <b...@nicira.com> wrote:
>
> > Signed-off-by: Ben Pfaff <b...@nicira.com>
> > ---
> > utilities/ovs-vsctl.8.in | 6 ++++--
> > 1 files changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/utilities/ovs-vsctl.8.in b/utilities/ovs-vsctl.8.in
> > index a4a6766..d3d8849 100644
> > --- a/utilities/ovs-vsctl.8.in
> > +++ b/utilities/ovs-vsctl.8.in
> > @@ -558,8 +558,10 @@ follow the syntax for the column's key type and value
> > type,
> > respectively. When multiple pairs are present (separated by spaces or
> > a comma), duplicate keys are not allowed, and again the order is not
> > important. Duplicate values are allowed. An empty map is represented
> > -as \fB{}\fR, and curly braces may be optionally enclose non-empty maps
> > -as well.
> > +as \fB{}\fR. Curly braces may optionally enclose non-empty maps as
> > +well (but use quotes to prevent the shell from expanding
> > +\fBother-config={0=x,1=y}\fR into \fBother-config=0=x
> > +other-config=0=y\fR, which may not have the desired effect).
> > .
> > .ST "Database Command Syntax"
> > .IP "[\fB\-\-columns=\fIcolumn\fR[\fB,\fIcolumn\fR]...] \fBlist \fItable
> > \fR[\fIrecord\fR]..."
> > --
> > 1.7.2.5
> >
> > _______________________________________________
> > dev mailing list
> > dev@openvswitch.org
> > http://openvswitch.org/mailman/listinfo/dev
> >
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
