From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] network: fix network.sh -e option
Date: Wed, 14 Dec 2016 15:24:38 +0100 [thread overview]
Message-ID: <20161214142422.GC20141@rei.lan> (raw)
In-Reply-To: <20161130100720.3577-1-pvorel@suse.cz>
Hi!
> a94a669 added 's' to filename => rename to original version
Looks good to me.
Alexej: should we commit this rename or should we rather change the
filename in the network.sh script?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2016-12-14 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 10:07 [LTP] [PATCH 1/1] network: fix network.sh -e option Petr Vorel
2016-12-14 14:24 ` Cyril Hrubis [this message]
2016-12-14 15:03 ` Alexey Kodanev
2016-12-14 15:24 ` 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=20161214142422.GC20141@rei.lan \
--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.