From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: virtio-comment@lists.linux.dev
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [RFC PATCH v1 1/2] specvars.tex: Add \virtioauthor command
Date: Sun, 15 Sep 2024 10:56:30 +0300 [thread overview]
Message-ID: <v1-proposal-attachfiles-1.manos.pitsidianakis@linaro.org> (raw)
In-Reply-To: <v1-proposal-attachfiles.manos.pitsidianakis@linaro.org>
Add a macro that expands to the spec author "OASIS Virtual I/O Device
(VIRTIO) TC". This will be used in subsequent commits to define the
author of attached files in the pdf build.
Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
---
specvars.tex | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/specvars.tex b/specvars.tex
index a80557a..7d3c8f7 100644
--- a/specvars.tex
+++ b/specvars.tex
@@ -1,4 +1,5 @@
\input{setup-generated.tex}
+\newcommand{\virtioauthor}{OASIS Virtual I/O Device (VIRTIO) TC}
\newcommand{\virtioversion}{Virtual I/O Device (VIRTIO) Version \virtiorev}
\newcommand{\virtiospecfile}{virtio-v\virtiorev-\virtiodraftstage\virtioworkingdraft}
\newcommand{\virtiourlbase}{https://docs.oasis-open.org/virtio/virtio/v\virtiorev/\virtiodraftstage\virtioworkingdraft}
@@ -15,7 +16,7 @@
% PDF setup
\hypersetup{
-pdfauthor = {OASIS Virtual I/O Device (VIRTIO) TC},
+pdfauthor = {\virtioauthor},
pdftitle = {Virtual I/O Device (VIRTIO) Version \virtiorev},
pdfsubject = {Virtual I/O Device (VIRTIO) Version \virtiorev},
pdfkeywords = {VIRTIO, Virtual I/O Device},
--
γαῖα πυρί μιχθήτω
next prev parent reply other threads:[~2024-09-15 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 7:56 [RFC PATCH v1 0/2] Embed files as PDF attachments Manos Pitsidianakis
2024-09-15 7:56 ` Manos Pitsidianakis [this message]
2024-09-15 7:56 ` [RFC PATCH v1 2/2] Embed virtio-queue.h as PDF attachment Manos Pitsidianakis
2024-09-15 11:11 ` [RFC PATCH v1 0/2] Embed files as PDF attachments Michael S. Tsirkin
2024-09-15 11:31 ` Manos Pitsidianakis
2024-09-15 11:56 ` Michael S. Tsirkin
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=v1-proposal-attachfiles-1.manos.pitsidianakis@linaro.org \
--to=manos.pitsidianakis@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=virtio-comment@lists.linux.dev \
/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