Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: virtio-dev@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [RFC PATCH  0/8] some tweaks to the document build process
Date: Fri, 27 Mar 2020 11:53:38 +0100	[thread overview]
Message-ID: <20200327115338.57a79ac4.cohuck@redhat.com> (raw)
In-Reply-To: <20200327103803.10460-1-alex.bennee@linaro.org>

On Fri, 27 Mar 2020 10:37:55 +0000
Alex Bennée <alex.bennee@linaro.org> wrote:

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

OASIS requirements are my concern here as well.

> 
> What do people think? Is this worth improving on?
> 
> Alex Bennée (8):
>   README.md: convert html to proper Markdown format
>   CONTRIBUTING.md: convert to proper MarkDown
>   LICENSE.md: convert html to proper MarkDown

We should double-check first if the html snippets in there are sourced
into some official web page somewhere. If not, I'm all for converting
this.

>   makeall.sh: add explicit shebang to script
>   Cleanup old changelog files

I'm not sure if there are any requirements for keeping this -- even if
they are available in the history forever.

>   Remove all mentioned of subversion

That's probably fine.

>   make*: remove reliance on REVISION-DATE and use git
>   Makefile: add simple make automation with clean target
> 
>  CONTRIBUTING.md         |   22 +-
>  LICENSE.md              |    9 +-
>  Makefile                |   17 +
>  README.md               |  258 ++++------
>  REVISION-DATE           |    1 -
>  cl-cs01.tex             |   86 ----
>  cl-cs02.tex             |   52 --
>  cl-cs03.tex             |  328 ------------
>  cl-cs04.tex             |  134 -----
>  cl-csprd02.tex          | 1043 ---------------------------------------
>  cl-csprd03.tex          |  400 ---------------
>  getchangelog.pl         |  114 -----
>  git-svn.txt             |   34 --
>  make-setup-generated.sh |   54 +-
>  makeall.sh              |    3 +-
>  makediff.sh             |    1 -
>  makediffall.sh          |    1 -
>  makediffwithbase.sh     |    1 -
>  maketex.sh              |    1 -
>  makezip.sh              |   11 +-
>  20 files changed, 169 insertions(+), 2401 deletions(-)
>  create mode 100644 Makefile
>  delete mode 100644 REVISION-DATE
>  delete mode 100644 cl-cs01.tex
>  delete mode 100644 cl-cs02.tex
>  delete mode 100644 cl-cs03.tex
>  delete mode 100644 cl-cs04.tex
>  delete mode 100644 cl-csprd02.tex
>  delete mode 100644 cl-csprd03.tex
>  delete mode 100755 getchangelog.pl
>  delete mode 100644 git-svn.txt
> 


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-03-27 10:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 10:37 [virtio-comment] [RFC PATCH 0/8] some tweaks to the document build process Alex Bennée
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 1/8] README.md: convert html to proper Markdown format Alex Bennée
2020-04-30  7:39   ` [virtio-comment] Re: [virtio-dev] " Michael S. Tsirkin
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 2/8] CONTRIBUTING.md: convert to proper MarkDown Alex Bennée
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 3/8] LICENSE.md: convert html " Alex Bennée
2020-03-27 10:37 ` [virtio-comment] [RFC PATCH 4/8] makeall.sh: add explicit shebang to script Alex Bennée
2020-03-27 10:47   ` Cornelia Huck
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 5/8] Cleanup old changelog files Alex Bennée
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 6/8] Remove all mentioned of subversion Alex Bennée
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 7/8] make*: remove reliance on REVISION-DATE and use git Alex Bennée
2020-03-27 10:38 ` [virtio-comment] [RFC PATCH 8/8] Makefile: add simple make automation with clean target Alex Bennée
2020-03-27 10:53 ` Cornelia Huck [this message]
2020-03-27 11:58   ` [virtio-comment] [RFC PATCH 0/8] some tweaks to the document build process Alex Bennée
2020-04-06 11:14 ` [virtio-comment] " Alex Bennée
  -- strict thread matches above, loose matches on Subject: below --
2020-03-24 18:28 [virtio-comment] " Alex Bennée
2020-03-24 17:54 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=20200327115338.57a79ac4.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@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