From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-comment@lists.linux.dev
Subject: Re: [PATCH v2 08/10] make-setup-generated: optionally add GIT metadata
Date: Fri, 10 Oct 2025 14:10:25 +0100 [thread overview]
Message-ID: <87ms5yx5q6.fsf@draig.linaro.org> (raw)
In-Reply-To: <20251010074157-mutt-send-email-mst@kernel.org> (Michael S. Tsirkin's message of "Fri, 10 Oct 2025 07:52:24 -0400")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Fri, Oct 10, 2025 at 12:20:08PM +0100, Alex Bennée wrote:
<snip>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Message-ID: <20251008145916.2626143-8-alex.bennee@linaro.org>
>
> Pls avoid Message-ID trailers in patches you post. It's really
> confusing.
That was added by b4 - I can add a .b4-config to stop that happening
accidentally. I see the git history has Links instead, e.g.:
Link: https://lore.kernel.org/r/20250305164546.1484029-1-mvaralar@redhat.com
is that OK?
>
>> ---
>> make-setup-generated.sh | 32 ++++++++++++++++++++++++++++----
>> makeall.sh | 4 ++--
>> makehtml.sh | 2 +-
>> makepdf.sh | 2 +-
>> 4 files changed, 32 insertions(+), 8 deletions(-)
>>
>> diff --git a/make-setup-generated.sh b/make-setup-generated.sh
>> index 2c5c7f8..8d33ac5 100755
>> --- a/make-setup-generated.sh
>> +++ b/make-setup-generated.sh
>> @@ -1,16 +1,31 @@
>> #! /bin/sh
>> +#
>> +# Generate version and metadata preamble for the document
>> +#
>>
>> DATESTR=${DATESTR:-`cat REVISION-DATE 2>/dev/null`}
>> -if [ x"$DATESTR" = x ]; then
>> - ISODATE=`git show --format=format:'%cd' --date=iso | head -n 1`
>> - DATESTR=`date -d "$DATE" +'%d %B %Y'`
>> +
>> +# If a second argument is passed we extract what we can from git
>> +# metadata (closest lightweight tag) and local tree status. This
>> +# allows locally generated copies to be tagged appropriately.
>> +#
>> +# The formal build process skips this.
>> +if ! test -z "$2"; then
>> + TAG=$(git describe --dirty --tags)
>> + # base date on now
>> + DATESTR=$(date +'%d %B %Y')
>> + COMMIT=$(git rev-parse --short HEAD)
>> +
>> + # Finally check if we have un-committed changes in the tree
>> + if ! git diff-index --quiet HEAD -- ; then
>> + COMMIT="$COMMIT with local changes"
>> + fi
>> fi
>>
>> case "$1" in
>> *-wd*)
>> STAGE=wd
>> STAGENAME="Working Draft"
>> - WORKINGDRAFT=`basename "$1" | sed 's/.*-wd//'`
>> ;;
>> *-os*)
>> STAGE=os
>
> This is used in the generated latex:
> make-setup-generated.sh:\newcommand{\virtioworkingdraft}{$WORKINGDRAFT}
>
> Are you sure output for a wd is unaffected?
> We still need to be able to generate these for the TC process.
>
>
>> @@ -41,6 +56,15 @@ esac
>>
>> VERSION=`echo "$1"| sed -e 's/virtio-v//' -e 's/-.*//'`
>>
>> +#
>> +# Finally if we are building a local draft copy append the commit
>> +# details to the end of the working draft
>> +#
>> +if ! test -z "$COMMIT" ; then
>> + STAGEEXTRATITLE="$STAGEEXTRATITLE (@ git $COMMIT)"
>> +fi
>> +
>> +
>> #Prepend OASIS unless already there
>> case "$STAGENAME" in
>> OASIS*)
>> diff --git a/makeall.sh b/makeall.sh
>> index 37e6c34..5f5d5dc 100755
>> --- a/makeall.sh
>> +++ b/makeall.sh
>> @@ -3,8 +3,8 @@
>> export SPECDOC=${SPECDOC:-`cat REVISION`}
>> export DATESTR=${DATESTR:-`cat REVISION-DATE`}
>> ./makezip.sh
>> -./makehtml.sh
>> -./makepdf.sh
>> +./makehtml.sh $1
>> +./makepdf.sh $1
>> zip $SPECDOC.zip $SPECDOC.pdf
>> echo Generated file $SPECDOC.zip
>> echo To change output file name, set SPECDOC environment variable
>> diff --git a/makehtml.sh b/makehtml.sh
>> index 45b7080..cf1a8d7 100755
>> --- a/makehtml.sh
>> +++ b/makehtml.sh
>> @@ -1,7 +1,7 @@
>> #!/bin/sh
>>
>> SPECDOC=${SPECDOC:-`cat REVISION`}
>> -./make-setup-generated.sh "$SPECDOC"
>> +./make-setup-generated.sh "$SPECDOC" $1
>>
>> cp virtio-html.tex $SPECDOC.tex
>>
>> diff --git a/makepdf.sh b/makepdf.sh
>> index 9cae903..bdfb8e5 100755
>> --- a/makepdf.sh
>> +++ b/makepdf.sh
>> @@ -1,7 +1,7 @@
>> #!/bin/sh
>>
>> SPECDOC=${SPECDOC:-`cat REVISION`}
>> -./make-setup-generated.sh "$SPECDOC"
>> +./make-setup-generated.sh "$SPECDOC" $1
>>
>> rm $SPECDOC.aux $SPECDOC.pdf $SPECDOC.out
>> xelatex --jobname $SPECDOC virtio.tex
>> --
>> 2.47.3
>>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-10-10 13:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 11:20 [PATCH v2 00/10] QoL tweaks and github action Alex Bennée
2025-10-10 11:20 ` [PATCH v2 01/10] LICENSE.md: convert html to proper MarkDown Alex Bennée
2025-10-30 7:10 ` Manos Pitsidianakis
2025-10-10 11:20 ` [PATCH v2 02/10] README.md: convert embedded " Alex Bennée
2025-10-10 11:20 ` [PATCH v2 03/10] REVISION: update to 1.4-wd01 Alex Bennée
2025-10-10 11:20 ` [PATCH v2 04/10] .gitpublish: update base to current working branch Alex Bennée
2025-10-10 11:20 ` [PATCH v2 05/10] virtio-html.tex: sort package list Alex Bennée
2025-10-10 11:20 ` [PATCH v2 06/10] specvars.tex: properly wrap arguments to \urldef Alex Bennée
2025-10-10 11:53 ` Michael S. Tsirkin
2025-10-10 13:49 ` Alex Bennée
2025-10-10 11:20 ` [PATCH v2 07/10] virtio-html.cfg: implement workaround for htlatex regression Alex Bennée
2025-10-10 11:20 ` [PATCH v2 08/10] make-setup-generated: optionally add GIT metadata Alex Bennée
2025-10-10 11:52 ` Michael S. Tsirkin
2025-10-10 13:10 ` Alex Bennée [this message]
2025-10-10 13:16 ` Michael S. Tsirkin
2025-10-10 13:48 ` Alex Bennée
2025-10-10 11:20 ` [PATCH v2 09/10] Makefile: add some simple make automations Alex Bennée
2025-10-10 11:20 ` [PATCH v2 10/10] .github: add a runner to build the latest draft Alex Bennée
2025-10-10 12:00 ` Michael S. Tsirkin
2025-10-10 13:58 ` Alex Bennée
2025-10-10 14:06 ` Michael S. Tsirkin
2025-10-10 12:06 ` [PATCH v2 00/10] QoL tweaks and github action 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=87ms5yx5q6.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=mst@redhat.com \
--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