From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/4] doc: Update style guide to new API
Date: Fri, 28 Feb 2020 04:22:08 -0500 (EST) [thread overview]
Message-ID: <513439094.9393483.1582881728087.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200228084236.GA4925@dell5510>
----- Original Message -----
> Hi Jan,
>
> > > Do we want to keep this document?
>
> > I agree to remove this old document.
>
> > > Wouldn't it be better to have this info in Test-Writing-Guidelines (to
> > > have a single document)?
>
> > Yes, and there are too much-duplicated contents in this, maybe we can
> > extract something useful to library-api-writing-guidelines.txt
> > and test-writing-guidelines.txt then delete it?
>
> 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.
>
> Kind regards,
> Petr
>
>
next prev parent reply other threads:[~2020-02-28 9:22 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 [this message]
2020-02-28 9:55 ` Petr Vorel
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=513439094.9393483.1582881728087.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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