From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/4] doc: Update style guide to new API
Date: Fri, 28 Feb 2020 15:24:55 +0800 [thread overview]
Message-ID: <CAEemH2ddNJTjzvPgHvtwVTM0CeFYH2_wy7SeK90ZPDMvME9K5g@mail.gmail.com> (raw)
In-Reply-To: <20200227163922.317-4-pvorel@suse.cz>
On Fri, Feb 28, 2020 at 12:39 AM Petr Vorel <pvorel@suse.cz> wrote:
> Document still needs more update, but at least don't use legacy API
> examples.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> 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?
>
> Kind regards,
> Petr
>
--
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20200228/208fa377/attachment.htm>
next prev parent reply other threads:[~2020-02-28 7:24 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 [this message]
2020-02-28 8:42 ` Petr Vorel
2020-02-28 9:22 ` Jan Stancek
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=CAEemH2ddNJTjzvPgHvtwVTM0CeFYH2_wy7SeK90ZPDMvME9K5g@mail.gmail.com \
--to=liwang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.