From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] network/stress: Update README
Date: Wed, 24 Jan 2018 14:21:05 +0100 [thread overview]
Message-ID: <20180124132104.GA32270@rei> (raw)
In-Reply-To: <20180124131043.dbufum2zn6ekrkzc@dell5510>
Hi!
> I'd propose to use simple relative path, e.g. INSTALL. Most of the projects use it (at
> least for files like README or INSTALL in root of source tree.
>
> Or, if we really need absolute path, lets use $LTPROOT, e.g. $LTPROOT/INSTALL.
Sounds good.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-01-24 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 9:29 [LTP] [PATCH 1/1] network/stress: Update README Petr Vorel
2018-01-24 11:18 ` Cyril Hrubis
2018-01-24 13:10 ` Petr Vorel
2018-01-24 13:21 ` Cyril Hrubis [this message]
2018-01-24 14:13 ` Petr Vorel
2018-01-24 14:18 ` 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=20180124132104.GA32270@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.