From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2 1/1] test.sh: colorize the output
Date: Tue, 24 Jan 2017 15:05:23 +0100 [thread overview]
Message-ID: <20170124140523.GF29054@rei.lan> (raw)
In-Reply-To: <20170124135900.kueiezajhxxgcu2h@dell5510>
Hi!
> I mean these:
> $ git grep -i "echo ltp-pan reported"
> testscripts/diskio.sh: echo ltp-pan reported PASS
> testscripts/diskio.sh: echo ltp-pan reported FAIL
> testscripts/network.sh: echo ltp-pan reported PASS
> testscripts/network.sh: echo ltp-pan reported FAIL
> testscripts/runEALtests.sh: echo ltp-pan reported PASS
> testscripts/runEALtests.sh: echo ltp-pan reported FAIL
>
> Not really important, just nice to have complete. It'd just use colors from
> tst_ansi_color.sh (separate color file).
Hmm, I wouldn't touch these scripts at all...
> > > * DOC: where to put docs?
>
> > I'm unsure as well. I guess that we can start a new file under doc/ if
> > we do not find a better fit.
>
> Syntax: plain doc or github markdown? Some of files are used for github wiki, but not all.
Well I started to use asciidoc for the documents before we moved to the
GitHub which uses markdown by default. However GitHub supports most of
the asciidoc syntax as well, so I would just continue using that.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2017-01-24 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 16:10 [LTP] [RFC PATCH v2 1/1] test.sh: colorize the output Petr Vorel
2017-01-23 12:12 ` Cyril Hrubis
2017-01-24 13:59 ` Petr Vorel
2017-01-24 14:05 ` Cyril Hrubis [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=20170124140523.GF29054@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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