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-Epba5tYJaz@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|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Serhei Makarov <me at serhei dot io> ---
A list of commonly recurring command line options (to guide future script
development). Perhaps put in future documentation:
- source_repo: project source code (e.g. to obtain a list of commits)
- branch: branch in source_repo to analyze
- project: restrict analysis to testruns tagged <project> (e.g. project=gdb)
- key: restrict analysis to testcases containing <key> (TODO: matching glob
<key>, see PR25349)
- baseline: baseline commit/run to compare against
- latest: commit/run to compare
- sort: recent/least_recent
- restrict: restrict output to N objects
- pretty: where available, pretty=html enables HTML output, pretty=no enables
JSON output
- compact: where available, for pretty=html enables a more compact view
- verbose
Incomplete list of options for log importing:
- raw_logs: collection of raw log files to import
- rebuild: rebuild entire repository (TODO: parse all files again and update
metadata, see PR25075)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-01-06 20:33 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 ` me at serhei dot io [this message]
2020-01-01 0:00 ` [Bug bunsen/25090] " me at serhei dot io
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-Epba5tYJaz@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).