From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: jin.li@windriver.com
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] number overcommit_memory test name in runtest/mm
Date: Wed, 31 Oct 2012 17:45:23 +0800 [thread overview]
Message-ID: <5090F333.1070608@cn.fujitsu.com> (raw)
In-Reply-To: <1351675894-4843-2-git-send-email-jin.li@windriver.com>
On 10/31/2012 05:31 PM, jin.li@windriver.com wrote:
> From: Jin Li <jin.li@windriver.com>
>
> ---
> runtest/mm | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/runtest/mm b/runtest/mm
> index 0f59ef7..a8bd605 100644
> --- a/runtest/mm
> +++ b/runtest/mm
Pushed, thank you.
Wanlong Gao
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-10-31 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 9:31 [LTP] number overcommit_memory test name in runtest/mm jin.li
2012-10-31 9:31 ` [LTP] [PATCH] " jin.li
2012-10-31 9:45 ` Wanlong Gao [this message]
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=5090F333.1070608@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=jin.li@windriver.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