From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eric Blake <eblake@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Kashyap Chamarthy <kchamart@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] qemu-img: Document --force-share / -U
Date: Fri, 8 Dec 2017 15:53:59 +0800 [thread overview]
Message-ID: <20171208075359.GD15798@lemon> (raw)
In-Reply-To: <874lp1k6n8.fsf@dusky.pond.sub.org>
On Fri, 12/08 08:42, Markus Armbruster wrote:
> Fam Zheng <famz@redhat.com> writes:
>
> > On Thu, 12/07 10:53, Eric Blake wrote:
> >> On 12/07/2017 04:58 AM, Kashyap Chamarthy wrote:
> >> > On Thu, Dec 07, 2017 at 04:44:53PM +0800, Fam Zheng wrote:
> [...]
> >> >> +it less likely to conflict with a running guest's permissions due to image
> >> >> +locking. For example, this can be used to get the image information (with
> >> >> +'info' subcommand) when the image is used by a running guest. Note that this
> >> >> +could produce inconsistent result because of concurrent metadata changes, etc..
> >> >
> >> > Super nit-pick: an ellipsis[*] is three dots :-), so, when applying you
> >> > might want to: s/../.../
> >> >
> >> > [*] https://dictionary.cambridge.org/dictionary/english/ellipsis
> >>
> >> Except that both "etc." and "..." independently convey a sense of
> >> continuation, which means that using both at once is both redundant
> >> (just one will do) and difficult to argue how to typeset (since 'etc.'
> >> is often written with an explicit '.' to emphasize that is an
> >> abbreviation, does that mean you have to write 'etc.''...' for a total
> >> of 4 dots?).
> >
> > I have the impression that "etc." is more correct than "etc"
>
> It is.
>
> > so I used even at
> > the end of the sensence where there is another period '.', making it "etc..".
>
> That's wrong all the same :)
>
> https://en.wikipedia.org/wiki/Period_(punctuation)#Abbreviations
>
> > If ending the paragraph with "etc." is enough, we can drop one ".".
>
> Please do.
Yes, thanks, v2 sent.
Fam
prev parent reply other threads:[~2017-12-08 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 8:44 [Qemu-devel] [PATCH] qemu-img: Document --force-share / -U Fam Zheng
2017-12-07 10:58 ` [Qemu-devel] [Qemu-block] " Kashyap Chamarthy
2017-12-07 16:53 ` Eric Blake
2017-12-08 1:41 ` Fam Zheng
2017-12-08 7:42 ` Markus Armbruster
2017-12-08 7:53 ` Fam Zheng [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=20171208075359.GD15798@lemon \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kchamart@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).