From: chrubis@suse.cz
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] readdir/readdir03.c: add new error number testes
Date: Wed, 7 May 2014 11:09:31 +0200 [thread overview]
Message-ID: <20140507090930.GA18644@rei> (raw)
In-Reply-To: <1399427555.2397.8.camel@G08JYZSD130126>
Hi!
> > > Yes, I am aware that.
> > > Could I create a new directory to do that or others?
> >
> > Not necessarily. At least add a note about this in the comment at the
> > start of the testcase, and maybe we should start the test numbers at 21.
> >
>
> OK. I will add a note.
> BTW, do you mean that we start the test at May 21.
Just thought that it could be better to number the readdir(3) testcases
starting from 01 and readdir(2) (syscall ones) from 21 so that you can
tell from the testcase number which readdir it tests.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-05-07 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 11:12 [LTP] [PATCH] readdir/readdir03.c: add new error number testes Zeng Linggang
2014-05-05 16:32 ` chrubis
[not found] ` <1399373430.3177.55.camel@G08JYZSD130126>
2014-05-06 11:00 ` chrubis
[not found] ` <1399427555.2397.8.camel@G08JYZSD130126>
2014-05-07 9:09 ` chrubis [this message]
[not found] ` <1399459901.2397.18.camel@G08JYZSD130126>
2014-05-07 12:58 ` [LTP] [PATCH v2 2/2] readdir/readdir21.c: " chrubis
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=20140507090930.GA18644@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=zenglg.jy@cn.fujitsu.com \
/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