<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 10, 2024 at 11:54 AM Aaron Conole <<a href="mailto:aconole@redhat.com">aconole@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Adam Hassick <<a href="mailto:ahassick@iol.unh.edu" target="_blank">ahassick@iol.unh.edu</a>> writes:<br>
<br>
> This script takes in a URL to a series on Patchwork and emits a<br>
> tarball which may be used for running tests.<br>
><br>
> Signed-off-by: Adam Hassick <<a href="mailto:ahassick@iol.unh.edu" target="_blank">ahassick@iol.unh.edu</a>><br>
> ---<br>
<br>
Just a quick glance.<br>
<br>
Is it possible to include a doc on how it is expected to run this<br>
script? Maybe that could help to also evaluate it as well.<br></blockquote><div><br></div><div>I was thinking along similar lines when I ran the script, but to a certain extent it seemed like having helpful examples in the config file would clear up confusion. Nevertheless, I think it's certainly worth writing the process down a little more. I wonder should we instead follow the example of pw_maintainers_cli.py and have the example usage, how to run, etc. written as a string at the top of the file? Then we are consistent with how other scripts in the repo are operating.</div></div></div>