From: Aaron Conole <aconole@redhat.com>
To: Adam Hassick <ahassick@iol.unh.edu>
Cc: ci@dpdk.org, alialnu@nvidia.com
Subject: Re: [PATCH v1] tools: Update create_series_artifact script
Date: Tue, 23 Jul 2024 09:03:19 -0400 [thread overview]
Message-ID: <f7tr0bkjm5k.fsf@redhat.com> (raw)
In-Reply-To: <20240717180642.24550-1-ahassick@iol.unh.edu> (Adam Hassick's message of "Wed, 17 Jul 2024 14:06:42 -0400")
Adam Hassick <ahassick@iol.unh.edu> writes:
> This is a collection of small changes to the create_artifact_script
> that the community lab has made over the past several months. The
> most notable change is the addition of the "branch" argument, which
> allows the caller to specify a branch to apply on.
>
> * Add branch override argument.
> * Default to main branch if guess_git_tree fails.
> * Return list of default patch tags if patch_parser fails.
> * Use patch name instead of database ID for the patch file name.
>
> Signed-off-by: Adam Hassick <ahassick@iol.unh.edu>
> ---
Thanks, applied!
prev parent reply other threads:[~2024-07-23 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 18:06 Adam Hassick
2024-07-23 13:03 ` Aaron Conole [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=f7tr0bkjm5k.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.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 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).