From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] open posix testsuite and names of testcases
Date: Mon, 11 Feb 2013 15:38:38 +0100 [thread overview]
Message-ID: <20130211143838.GA2829@rei> (raw)
In-Reply-To: <50C08A4C.1090402@redhat.com>
Hi!
Just recently I've found that one of the posix tests stays running after
the testsuite has exited (is reparented to init and runs happily ever
after). Which is another usecase for this rename.
But the original patch was rather hack (and it doesn't work for me
anyway).
So what about renaming the sources itself? Do we agree on this?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-02-11 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 12:06 [LTP] open posix testsuite and names of testcases Jan Stancek
2012-12-06 14:13 ` chrubis
[not found] ` <878595998.11610861.1354808151182.JavaMail.root@redhat.com>
2012-12-06 16:35 ` chrubis
2012-12-06 14:14 ` Wanlong Gao
2012-12-06 14:27 ` chrubis
2013-02-11 14:38 ` chrubis [this message]
[not found] ` <652016734.705678.1360596388811.JavaMail.root@redhat.com>
2013-02-11 15:51 ` chrubis
[not found] <605746806.1323310.1360671766487.JavaMail.root@redhat.com>
[not found] ` <51218CB1.8040709@cn.fujitsu.com>
2013-02-27 14:38 ` chrubis
2013-02-27 17:11 ` chrubis
2013-04-23 13:48 ` chrubis
[not found] ` <1822042882.3039242.1366879006975.JavaMail.root@redhat.com>
2013-04-25 10:42 ` 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=20130211143838.GA2829@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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