From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] [PATCH] commands/which01.sh: Fix test for debian.
Date: Fri, 5 May 2017 11:18:12 +0200 [thread overview]
Message-ID: <20170505091812.GA16729@rei.suse.de> (raw)
In-Reply-To: <94622407.7415649.1493924848056.JavaMail.zimbra@redhat.com>
Hi!
> No objections - I think we used same approach in file test.
> I'd add also that note about POSIX not defining it to commit message.
I've rewritten the commit description a bit to include this piece of
information and pushed.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2017-05-05 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 14:50 [LTP] [RFC] [PATCH] commands/which01.sh: Fix test for debian Cyril Hrubis
2017-05-04 19:07 ` Jan Stancek
2017-05-05 9:18 ` Cyril Hrubis [this message]
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=20170505091812.GA16729@rei.suse.de \
--to=chrubis@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