From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <george.dunlap@cloud.com>, Julien Grall <julien@xen.org>
Cc: xen-devel@lists.xenproject.org, michal.orzel@amd.com,
ayan.kumar.halder@amd.com, Julien Grall <jgrall@amazon.com>,
Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH] SUPPORT.MD: Fix matrix generation after 43c416d0d819 and 77c39a53cf5b
Date: Fri, 15 Mar 2024 10:35:59 +0000 [thread overview]
Message-ID: <8bffbeea-c1fb-4858-b20c-09ad5d52c71c@citrix.com> (raw)
In-Reply-To: <CA+zSX=aBxfnm7fjrVf+0_oQn32MsEkZbWQ4MC+UDxSePea+NoQ@mail.gmail.com>
On 15/03/2024 10:05 am, George Dunlap wrote:
> On Thu, Mar 14, 2024 at 5:39 PM Julien Grall <julien@xen.org> wrote:
>> From: Julien Grall <jgrall@amazon.com>
>>
>> The script docs/support-matrix-generate throw the following error on the
>> latest staging.
> I wonder if it would be worth adding a follow-up patch to run that
> script, maybe only when debug=y, so it catches errors in development.
I have a second docs thing which needs doing in some copious free
never. The Sphinx build is getting broken occasionally and I'm the only
one who notices.
I was intending to have a Gitlab run specifically for docs, although the
container for it is going to need to be giant to get all of our ad-hoc
dependencies.
~Andrew
prev parent reply other threads:[~2024-03-15 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 17:39 [PATCH] SUPPORT.MD: Fix matrix generation after 43c416d0d819 and 77c39a53cf5b Julien Grall
2024-03-14 17:41 ` Andrew Cooper
2024-03-14 17:42 ` Julien Grall
2024-03-15 10:05 ` George Dunlap
2024-03-15 10:35 ` Andrew Cooper [this message]
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=8bffbeea-c1fb-4858-b20c-09ad5d52c71c@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=george.dunlap@cloud.com \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.