From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2 0/3] Remove some userspace related tests
Date: Mon, 1 Oct 2018 03:59:33 -0400 (EDT) [thread overview]
Message-ID: <815877049.55263149.1538380773644.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180927145720.31014-1-pvorel@suse.cz>
----- Original Message -----
> Hi,
>
> Changes v1->v2:
> change in 3rd patch:
> * at: removed at_allow01, at_deny01, Makefiles
> * Removed also su and acls tests.
I don't have objections, ack set.
next prev parent reply other threads:[~2018-10-01 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 14:57 [LTP] [RFC PATCH v2 0/3] Remove some userspace related tests Petr Vorel
2018-09-27 14:57 ` [LTP] [RFC PATCH v2 1/3] testscripts: Remove EAL2 testsuite script Petr Vorel
2018-09-27 14:57 ` [LTP] [RFC PATCH v2 2/3] net: Remove network_commands (ftp, ssh) Petr Vorel
2018-09-27 14:57 ` [LTP] [RFC PATCH v2 3/3] Remove admin_tools test Petr Vorel
2018-09-28 2:17 ` [LTP] [RFC PATCH v2 0/3] Remove some userspace related tests Xiao Yang
2018-10-01 7:59 ` Jan Stancek [this message]
2018-10-01 12:56 ` 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=815877049.55263149.1538380773644.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