Streamlining code base?
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | cyclicdeadline: Streamline usage output and man pagesrc/ src/ | +33 | 0 replies | |
| 2/4 | deadline_test: Streamline usage output and man pagesrc/ src/ | +41 | 0 replies | |
| 3/4 | oslat: Streamline usage output and man pagesrc/ src/ | +38 | 0 replies | |
| 4/4 | oslat: Use string parser utiliessrc/ src/ src/ | +33 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [rt-tests 0/4] Streamlining code base?
Hi Clark and John,
I'd like to streamline all tools, so that the usage, command arguments and the output is more consistent. Every tool seems to be a bit different which makes all automatization around the tools more complex than needed.
Eventually, I'd like to add an easy machine parseable output from all tools. So what do you think? Stupid effort, go away?
Here are a bunch of patches to illustrate what I mean. Before invest too much time I'd like to discuss it, e.g. format.
Cheers,
Daniel
Daniel Wagner (4):
cyclicdeadline: Streamline usage output and man page
deadline_test: Streamline usage output and man page
oslat: Streamline usage output and man page
oslat: Use string parser utilies
src/include/rt-utils.h | 1 + src/lib/rt-utils.c | 30 ++++++ src/oslat/oslat.8 | 2 +- src/oslat/oslat.c | 143 ++++++++-------------------- src/sched_deadline/cyclicdeadline.8 | 24 ++--- src/sched_deadline/cyclicdeadline.c | 41 ++++---- src/sched_deadline/deadline_test.8 | 37 ++++--- src/sched_deadline/deadline_test.c | 47 +++++---- 8 files changed, 145 insertions(+), 180 deletions(-)
Signature · 1 line
2.28.0