Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: virtio-comment@lists.oasis-open.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [virtio-comment] Re: [PATCH  v2 0/5] some tweaks to the document build process
Date: Tue, 14 Jul 2020 21:27:21 +0100	[thread overview]
Message-ID: <87v9ipyh92.fsf@linaro.org> (raw)
In-Reply-To: <20200619204959.7877-1-alex.bennee@linaro.org>


Alex Bennée <alex.bennee@linaro.org> writes:

> Hi,
>
> So this is a re-spin of the series I sent earlier this year. I cut out
> all the radical trimming of changelogs and automation of the version
> stuff. You can still do a local build which will annotate the files
> with some version data which will hopefully help with draft copies.
>
> I've converted more of the htmlised markdown boilerplate into pure
> markdown. The text itself is unchanged.
>
> The makefile automation is mainly for my benefit - it just makes it
> easier to hit C-c c in emacs and trigger the compile-command. I
> realise this isn't useful for everyone so feel free to drop if it is
> an over imposition.

Ping? No interest?

-- 
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/


      parent reply	other threads:[~2020-07-14 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 20:49 [virtio-comment] [PATCH v2 0/5] some tweaks to the document build process Alex Bennée
2020-06-19 20:49 ` [virtio-comment] [PATCH v2 1/5] README.md: convert html to proper Markdown format Alex Bennée
2020-06-19 20:49 ` [virtio-comment] [PATCH v2 2/5] CONTRIBUTING.md: convert html to proper MarkDown Alex Bennée
2020-06-19 20:49 ` [virtio-comment] [PATCH v2 3/5] LICENSE.md: " Alex Bennée
2020-06-19 20:49 ` [virtio-comment] [PATCH v2 4/5] Makefile: add some simple make automations Alex Bennée
2020-06-19 20:49 ` [virtio-comment] [PATCH v2 5/5] make-setup-generated: optionally add GIT metadata Alex Bennée
2020-07-14 20:27 ` Alex Bennée [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=87v9ipyh92.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox