From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2 1/4] rpc-tirpc: Detect libtirpc with pkg-config
Date: Wed, 5 Feb 2020 10:53:48 +0100 [thread overview]
Message-ID: <20200205095348.GA17830@dell5510> (raw)
In-Reply-To: <20200204152430.10935-2-pvorel@suse.cz>
Hi,
> 136 files changed, 183 insertions(+), 333 deletions(-)
> delete mode 100644 testcases/network/rpc/rpc-tirpc/tests_pack/rpc_suite/rpc/rpc_auth_auth_destroy/rpc_auth_destroy.c
> delete mode 100644 testcases/network/rpc/rpc-tirpc/tests_pack/rpc_suite/rpc/rpc_createdestroy_clntraw_create/rpc_clntraw_create.c
These 2 files I deleted by accident, they need to stay.
Sorry for the noise.
Kind regards,
Petr
next prev parent reply other threads:[~2020-02-05 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:24 [LTP] [RFC PATCH v2 0/4] TI-RPC: enhancements (pkg-config, travis) Petr Vorel
2020-02-04 15:24 ` [LTP] [RFC PATCH v2 1/4] rpc-tirpc: Detect libtirpc with pkg-config Petr Vorel
2020-02-05 9:53 ` Petr Vorel [this message]
2020-02-28 16:44 ` Petr Vorel
2020-02-04 15:24 ` [LTP] [RFC PATCH v2 2/4] rpc: Fix build under glibc only TI-RPC implementation Petr Vorel
2020-02-04 15:24 ` [LTP] [RFC PATCH v2 3/4] travis: Merge debian.cross-compile.*.sh Petr Vorel
2020-02-04 15:24 ` [LTP] [RFC PATCH v2 4/4] rpc-tirpc: Remove unused tests 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=20200205095348.GA17830@dell5510 \
--to=pvorel@suse.cz \
--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