From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v2 0/7] doc build updates and terminology definitions
Date: Fri, 07 Aug 2020 16:20:49 +0100 [thread overview]
Message-ID: <87h7tejxda.fsf@linaro.org> (raw)
In-Reply-To: <20200807132030.GD609387@stefanha-x1.localdomain>
Stefan Hajnoczi <stefanha@redhat.com> writes:
> The HTML -> Markdown conversion is hard to review.
>
> Can you share a command-line that reviewers can run to verify that the
> text is unchanged?
Hmm not sure - I just eyeballed the two in githubs web-ui. That said
I've just noticed some of the example code formatting is a little messed
up so I should tweak that.
--
Alex Bennée
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2020-08-07 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 15:42 [virtio-comment] [PATCH v2 0/7] doc build updates and terminology definitions Alex Bennée
2020-07-24 15:42 ` [virtio-comment] [PATCH v2 1/7] README.md: convert html to proper Markdown format Alex Bennée
2020-07-24 15:42 ` [virtio-comment] [PATCH v2 2/7] CONTRIBUTING.md: convert html to proper MarkDown Alex Bennée
2020-07-24 15:42 ` [virtio-comment] [PATCH v2 3/7] LICENSE.md: " Alex Bennée
2020-07-24 15:42 ` [virtio-comment] [PATCH v2 4/7] Makefile: add some simple make automations Alex Bennée
2020-07-24 15:42 ` [virtio-comment] [PATCH v2 5/7] make-setup-generated: optionally add GIT metadata Alex Bennée
2020-07-24 15:42 ` [virtio-comment] [PATCH v2 6/7] introduction.tex: introduce a glossary of terms Alex Bennée
2020-08-07 13:18 ` [virtio-comment] " Stefan Hajnoczi
2020-07-24 15:42 ` [virtio-comment] [PATCH v2 7/7] content.tex: tighten up the definition of notification Alex Bennée
2020-08-05 13:57 ` [virtio-comment] Re: [PATCH v2 0/7] doc build updates and terminology definitions Alex Bennée
2020-08-07 13:20 ` [virtio-comment] " Stefan Hajnoczi
2020-08-07 15:20 ` Alex Bennée [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-24 15:38 Alex Bennée
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=87h7tejxda.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.