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

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

[Alex Bennée]

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?

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
  makeall.sh: add explicit shebang to script
  Cleanup old changelog files
  Remove all mentioned of subversion
  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

-- 
2.20.1


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/

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

[Alex Bennée]

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/

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

[Alex Bennée]

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?

Ping? Any other feedback?

> 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
>   makeall.sh: add explicit shebang to script
>   Cleanup old changelog files
>   Remove all mentioned of subversion
>   make*: remove reliance on REVISION-DATE and use git

I've been looking at other OASIS zipfiles and I think I could dump
REVISION as well as it's all in the rendered docs.


>   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


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