From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 3/3] build.sh: Allow to overwrite prefix
Date: Wed, 13 Dec 2017 14:59:43 +0100 [thread overview]
Message-ID: <20171213135943.GF11493@rei> (raw)
In-Reply-To: <20171213131334.26863-1-pvorel@suse.cz>
Hi!
> I like getopt(s) and the reason I didn't use them is:
> * I don't like short opts which provides getopts build-in (the one we use in LTP).
Why so, readability concerns?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-12-13 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 13:13 [LTP] [RFC PATCH 3/3] build.sh: Allow to overwrite prefix Petr Vorel
2017-12-13 13:59 ` Cyril Hrubis [this message]
2017-12-13 14:41 ` Petr Vorel
2017-12-13 16:12 ` Cyril Hrubis
2017-12-14 19:19 ` 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=20171213135943.GF11493@rei \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.