From: jspewock@iol.unh.edu
To: ci@dpdk.org
Cc: aconole@redhat.com, alialnu@nvidia.com, probb@iol.unh.edu,
Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v3 0/1] tools: Add script for getting rerun requests
Date: Thu, 21 Sep 2023 15:55:30 -0400 [thread overview]
Message-ID: <20230921195637.11369-3-jspewock@iol.unh.edu> (raw)
From: Jeremy Spewock <jspewock@iol.unh.edu>
This version adds a command-line argument to optionally use a different
URL for the patchworks API instead of always using the DPDK patchworks.
It will still default to using the DPDK patchworks however so this isn't
required.
v1: https://mails.dpdk.org/archives/ci/2023-September/002562.html
v2: https://mails.dpdk.org/archives/ci/2023-September/002568.html
Jeremy Spewock (1):
tools: add get_reruns script
tools/get_reruns.py | 233 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 233 insertions(+)
create mode 100755 tools/get_reruns.py
--
2.42.0
next reply other threads:[~2023-09-21 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 19:55 jspewock [this message]
2023-09-21 19:55 ` [PATCH v3 1/1] tools: add get_reruns script jspewock
2023-10-12 13:00 ` Aaron Conole
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=20230921195637.11369-3-jspewock@iol.unh.edu \
--to=jspewock@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
/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;
as well as URLs for NNTP newsgroup(s).