From: chrubis@suse.cz
To: ???? <eeslook@163.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Fw:Re: [ltp] ltp / testscripts / ltpstress.sh #line 257 : error command format for sar (#10)
Date: Thu, 10 Apr 2014 18:36:55 +0200 [thread overview]
Message-ID: <20140410163655.GB25778@rei> (raw)
In-Reply-To: <19a2d985.16036.14520092241.Coremail.eeslook@163.com>
Hi!
> Attach the patch file for fix sar command error.
>
>
> -------- ???????????? --------
> ????????"Cyril Hrubis" <notifications@github.com>
> ??????????2014-04-01 21:23:33
> ????????linux-test-project/ltp <ltp@noreply.github.com>
> ????????look <eeslook@163.com>
> ??????Re: [ltp] ltp / testscripts / ltpstress.sh #line 257 : error command format for sar (#10)
>
>
> Can you please send a patch to the LTP mailing list?
Can you also write short commit message (with kernel like Signed-of-by:
line) that explains the change?
I've looked at the systat pages and the looks like zero was never
supported as a number of iterations (but may have been wrongly accepted
some time ago).
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-04-10 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 1:24 [LTP] Fw:Re: [ltp] ltp / testscripts / ltpstress.sh #line 257 : error command format for sar (#10) 李奎
2014-04-10 16:36 ` chrubis [this message]
[not found] ` <5534fca.23dd.1454e729368.Coremail.eeslook@163.com>
2014-04-29 11:11 ` 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=20140410163655.GB25778@rei \
--to=chrubis@suse.cz \
--cc=eeslook@163.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