From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/4] doc: Update style guide to new API
Date: Fri, 28 Feb 2020 10:55:25 +0100 [thread overview]
Message-ID: <20200228095525.GA11177@dell5510> (raw)
In-Reply-To: <513439094.9393483.1582881728087.JavaMail.zimbra@redhat.com>
Hi Jan,
> > You often quote the style guide. What do you suggest?
> > Keep it or delete and move some of it's content to Test-Writing-Guidelines?
> > (which ones)?
> I'm fine with removing it, and move what's not covered to other docs.
Thanks for your ack.
To be honest I don't see much things left.
"Fixing Open Posix Testsuite" paragraph is not covered anywhere, but I wouldn't
care (not really sure where to put this + IMHO I'd prefer this project to be on
it's own).
For things like "Inline assigments" we get compiler warnings.
Maybe "System headers" note is worth. But actually, even this is outdated:
IMHO would be better to advice use our lapi headers (adding paragraph to
"2.2.1 Basic test structure"
Kind regards,
Petr
next prev parent reply other threads:[~2020-02-28 9:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 16:39 [LTP] [PATCH 1/4] Avoid using tst_res(TBROK) Petr Vorel
2020-02-27 16:39 ` [LTP] [PATCH 2/4] lib: Check also flags for tst_res() Petr Vorel
2020-02-28 7:00 ` Li Wang
2020-02-28 7:05 ` Petr Vorel
2020-02-28 12:13 ` Cyril Hrubis
2020-02-28 13:17 ` Petr Vorel
2020-02-28 14:17 ` Petr Vorel
2020-02-27 16:39 ` [LTP] [PATCH 3/4] doc: Improve flags info Petr Vorel
2020-02-27 16:39 ` [LTP] [PATCH 4/4] doc: Update style guide to new API Petr Vorel
2020-02-28 7:24 ` Li Wang
2020-02-28 8:42 ` Petr Vorel
2020-02-28 9:22 ` Jan Stancek
2020-02-28 9:55 ` Petr Vorel [this message]
2020-03-04 11:38 ` Petr Vorel
2020-02-28 7:47 ` [LTP] [PATCH 1/4] Avoid using tst_res(TBROK) Li Wang
2020-02-28 8:46 ` Petr Vorel
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=20200228095525.GA11177@dell5510 \
--to=pvorel@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