From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: <dsterba@suse.cz>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
<takeuchi_satoru@jp.fujitsu.com>
Subject: Re: [PATCH v3] btrfs-progs: Documentation: add T/P/E description for resize cmd
Date: Mon, 5 Jan 2015 09:42:24 +0800 [thread overview]
Message-ID: <1420422144.2384.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20150102162143.GC6114@twin.jikos.cz>
On Fri, 2015-01-02 at 17:21 +0100, David Sterba wrote:
> On Fri, Jan 02, 2015 at 05:12:04PM +0100, David Sterba wrote:
> > On Thu, Jan 01, 2015 at 08:27:55PM -0700, Chris Murphy wrote:
> > > Small problem with the rendering of this commit
> > > d4ef1a06f8be623ae94e4d498c306e8dd1605bef, when I use 'man btrfs
> > > filesystem' the above portion looks like this:
> > >
> > > 'K', 'M', 'G', 'T', 'P', or 'E\',
> > >
> > > I'm not sure why there's a trailing slash after the E.
> >
> > Me neither, but it looks like a bug in the asciidoc processing.
>
> Seems that only the first ' has to be quoted, and consumes the next
> unquoted ' as a pair, so with the last \' the next one is missing and
> is printed verbatim:
>
> Fixed by:
>
> -units designators: \'K\', \'M\', \'G\', \'T\', \'P\', or \'E\', which represent
> +units designators: \'K', \'M', \'G', \'T', \'P', or \'E', which represent
>
Oh, sorry, I missed this problem, thanks for fixing it.
-Gui
prev parent reply other threads:[~2015-01-05 1:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 2:01 [PATCH] btrfs-progs: Documentation: add T/P/E description for resize cmd Gui Hecheng
2014-12-22 3:20 ` Satoru Takeuchi
2014-12-22 7:22 ` [PATCH v2] " Gui Hecheng
2014-12-29 16:07 ` David Sterba
2014-12-30 1:23 ` Gui Hecheng
2014-12-30 1:52 ` [PATCH v3] " Gui Hecheng
2015-01-02 3:27 ` Chris Murphy
2015-01-02 16:12 ` David Sterba
2015-01-02 16:21 ` David Sterba
2015-01-05 1:42 ` Gui Hecheng [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=1420422144.2384.6.camel@localhost.localdomain \
--to=guihc.fnst@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=takeuchi_satoru@jp.fujitsu.com \
/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).