[virtio-comment] Re: [RFC PATCH 0/8] some tweaks to the document build process

["Alex Bennée" <alex.bennee@linaro.org>]

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

> Hi,
>
> I was reviewing someones virtio-spec and realised that I wasn't quite
> sure what it had been built from. Seeing as the standard is hosted in
> git I've tried to clean up some of the automation to make it clearer
> what a particular rendering was built from. Going forward it would be
> nice to use signed annotated tags for the final build version but I
> don't know how much of the boilerplate is down to OASIS requirements.
>
> What do people think? Is this worth improving on?

Apologies - my git send-email seems to be playing up. I'll re-send the
whole series once I've manually confirmed it's not cocking up the Cc
field. If anyone knows why I'm getting:

  Cc: virtio-comment@lists.oasis-open.org,
          =?UTF-8?q?Alex=20Benn=C3=A9e?= <alex.bennee@linaro.org>,
          Name,
          &lt,
          email&gt,
          br

In the sent email then please let me know. I thought I had my git setup
utf-8 clean already.

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