From: Jiri Jaburek <jjaburek@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 0/5] various tcp_cmds/ssh/* fixes, rewrites
Date: Mon, 06 Jan 2014 12:39:55 +0100 [thread overview]
Message-ID: <52CA960B.9080709@redhat.com> (raw)
In-Reply-To: <1386065776-1961-1-git-send-email-jjaburek@redhat.com>
On 12/03/2013 11:16 AM, Jiri Jaburek wrote:
> Jiri Jaburek (5):
> ssh: unify code style amongst ssh tests
> ssh: remove unused ssh_set_passwd script
> ssh: properly create/remove user home dir, if possible
> ssh: try to prevent invalid PASS when remote cmd fails
> ssh: don't use crypt-based pre-encrypted passwords
>
> testcases/network/tcp_cmds/ssh/ssh01 | 42 ++++++++++++------------
> testcases/network/tcp_cmds/ssh/ssh01_s1 | 39 +++++++++++++----------
> testcases/network/tcp_cmds/ssh/ssh02 | 39 +++++++++++------------
> testcases/network/tcp_cmds/ssh/ssh02_s1 | 17 +++++-----
> testcases/network/tcp_cmds/ssh/ssh03 | 46 +++++++++++++--------------
> testcases/network/tcp_cmds/ssh/ssh03_s1 | 15 +++++----
> testcases/network/tcp_cmds/ssh/ssh_set_passwd | 28 ----------------
> 7 files changed, 103 insertions(+), 123 deletions(-)
> delete mode 100755 testcases/network/tcp_cmds/ssh/ssh_set_passwd
>
Could somebody review these changes, please? All patches should be well
commented using commit messages.
Thanks,
Jiri
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-01-06 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 10:16 [LTP] [PATCH 0/5] various tcp_cmds/ssh/* fixes, rewrites Jiri Jaburek
2013-12-03 10:16 ` [LTP] [PATCH 1/5] ssh: unify code style amongst ssh tests Jiri Jaburek
2013-12-03 10:16 ` [LTP] [PATCH 2/5] ssh: remove unused ssh_set_passwd script Jiri Jaburek
2013-12-03 10:16 ` [LTP] [PATCH 3/5] ssh: properly create/remove user home dir, if possible Jiri Jaburek
2013-12-03 10:16 ` [LTP] [PATCH 4/5] ssh: try to prevent invalid PASS when remote cmd fails Jiri Jaburek
2013-12-03 10:16 ` [LTP] [PATCH 5/5] ssh: don't use crypt-based pre-encrypted passwords Jiri Jaburek
2014-01-06 11:39 ` Jiri Jaburek [this message]
2014-01-13 13:14 ` [LTP] [PATCH 0/5] various tcp_cmds/ssh/* fixes, rewrites Jan Stancek
2014-01-13 17:52 ` chrubis
2014-01-20 14:21 ` chrubis
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=52CA960B.9080709@redhat.com \
--to=jjaburek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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