[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171201145702.saqodo5qqh4ucbaq@crack.deadbeast.net>
Date: Fri, 1 Dec 2017 09:57:04 -0500
From: "G. Branden Robinson" <g.branden.robinson@...il.com>
To: Stefan Hajnoczi <stefanha@...hat.com>
Cc: "Jorgen S. Hansen" <jhansen@...are.com>,
"linux-man@...r.kernel.org" <linux-man@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Dexuan Cui <decui@...rosoft.com>
Subject: Re: [PATCH] vsock.7: document VSOCK socket address family
At 2017-12-01T13:09:01+0000, Stefan Hajnoczi wrote:
> On Thu, Nov 30, 2017 at 01:21:26PM +0000, Jorgen S. Hansen wrote:
> > > On Nov 30, 2017, at 12:21 PM, Stefan Hajnoczi <stefanha@...hat.com> wrote:
>
> Thanks for the quick review!
>
> I forgot to ask you: Is SOCK_DGRAM reliable and in-order over VMCI?
>
> > > +.PP
> > > +Valid socket types are
> > > +.B SOCK_STREAM
> > > +and
> > > +.B SOCK_DGRAM .
> >
> > The space here results in a space between SOCK_DGRAM and the “.” in the formatted text. Is that intentional?
>
> I haven't figured out the groff syntax to avoid the space :(. Any
> ideas?
What you want is the .BR macro.
.BR SOCK_DGRAM .
The man macro package defines six "two-font" macros for switching
between roman, bold, and italic faces without intervening space.
See man(7) and groff_man(7).
--
Regards,
Branden
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists