All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 2/2] README: Update developer section
Date: Mon, 31 Jul 2017 14:17:49 +0200	[thread overview]
Message-ID: <20170731121749.31271-2-rpalethorpe@suse.com> (raw)
In-Reply-To: <20170731121749.31271-1-rpalethorpe@suse.com>

Add the C tutorial and remove the comment about this being all the information
that is needed. That depends on the reader and the test they want to write or
edit.

Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
---
 README.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index ffe8c867b..ffa769d73 100644
--- a/README.md
+++ b/README.md
@@ -128,12 +128,13 @@ Before you start you should read following documents:
 * `doc/test-writing-guidelines.txt`
 * `doc/build-system-guide.txt`
 
-these two should contain all information needed for modifying or creating LTP
-testcases. If something is not covered there don't hesitate to ask on the LTP
-mailing list.
+There is also a step-by-step tutorial:
 
-Also note that these documents are available online at:
+* `doc/c-test-tutorial-simple.txt`
 
-https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines
+If something is not covered there don't hesitate to ask on the LTP mailing
+list. Also note that these documents are available online at:
 
+https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines
 https://github.com/linux-test-project/ltp/wiki/BuildSystem
+https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial
-- 
2.13.3


  reply	other threads:[~2017-07-31 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 12:17 [LTP] [PATCH v4 1/2] tutorial: Add a step-by-step C test tutorial Richard Palethorpe
2017-07-31 12:17 ` Richard Palethorpe [this message]
2017-08-02 13:38 ` Cyril Hrubis

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=20170731121749.31271-2-rpalethorpe@suse.com \
    --to=rpalethorpe@suse.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.