linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: "Uwe Kleine-König" <uwe@kleine-koenig.org>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] sindex.1: Use ' for a plain quote char
Date: Sat, 1 Aug 2020 18:41:44 +0200	[thread overview]
Message-ID: <20200801164144.bipofn3nximjc5ej@ltop.local> (raw)
In-Reply-To: <20200801154217.xwwv4nezijuqwfoa@comp-core-i7-2640m-0182e6>

On Sat, Aug 01, 2020 at 05:42:17PM +0200, Alexey Gladkov wrote:
> On Sat, Aug 01, 2020 at 02:40:04PM +0200, Luc Van Oostenryck wrote:
> > On Fri, Jul 31, 2020 at 11:41:25PM +0200, Uwe Kleine-König wrote:
> > > --- a/sindex.1
> > > +++ b/sindex.1
> > > @@ -128,8 +128,8 @@ struct member
> > >  .
> > >  .SH MODE
> > >  The \fBMODE\fR is dumped as a 3-letter string. The first letter denotes address
> > > -of part, 2-nd - access by value, 3-rd - access by pointer. A special value
> > > -\'\fIdef\fR\' means a symbol definition.
> > > +of part, 2-nd - access by value, 3-rd - access by pointer. A special
> > > +value '\fIdef\fR' means a symbol definition.
> > 
> > This looks good to me.
> > Thanks.
> > 
> > But maybe, in this case the single quotes are even not needed at all
> > since the symbol is already emphasized with the italic? Or the italic
> > is not needed because it's already between quotes?
> > Alexey, do you have any preferences?
> 
> Nop. If you think that this will be better, then I am OK with these
> changes.

OK, I think it's fine so.

I've applied it unchanged. Thanks to both of you.
-- Luc

      reply	other threads:[~2020-08-01 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 21:41 [PATCH] sindex.1: Use ' for a plain quote char Uwe Kleine-König
2020-08-01 12:40 ` Luc Van Oostenryck
2020-08-01 12:44   ` Uwe Kleine-König
2020-08-01 15:42   ` Alexey Gladkov
2020-08-01 16:41     ` Luc Van Oostenryck [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=20200801164144.bipofn3nximjc5ej@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=gladkov.alexey@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=uwe@kleine-koenig.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 NNTP newsgroup(s).