public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/25090] [v1.0] improved command line args parsing
Date: Wed, 01 Jan 2020 00:00:00 -0000	[thread overview]
Message-ID: <bug-25090-12167-kxanfTcOSp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25090-12167@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25090

Serhei Makarov <me at serhei dot io> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #2 from Serhei Makarov <me at serhei dot io> ---
A better format for specifying args would be, e.g.:

#!/usr/bin/env python3
from common.cmdline_args import default_args
info='''Walk the history of the specified branch (default master) of the Git
repo source_repo. For every commit, compare testruns under specified
project with testruns for the parent commit. Print a summary of how
test results change for testcases whose name contains the specified
substring <key>.'''
cmdline_args=default_args+[
  ('project', None, 'tags', 'restrict to testruns under <tags>'),
  ('key', None, 'glob', 'restrict to testcases matching <glob>'),
  ('source_repo', None, 'path', 'scan commits from source_repo'),
  ('branch', 'master', 'name', 'scan commits in branch <name>'),
]

A more informative usage message can then be generated from this data.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2020-01-13 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 [Bug bunsen/25090] New: " me at serhei dot io
2020-01-01  0:00 ` [Bug bunsen/25090] " me at serhei dot io
2020-01-01  0:00 ` me at serhei dot io [this message]
2022-09-16 17:42 ` [Bug bunsen/25090] Improve & standardize " serhei at serhei dot io

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=bug-25090-12167-kxanfTcOSp@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=bunsen@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).