From: Bian Naimeng <biannm@cn.fujitsu.com>
To: CAI Qian <caiqian@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH]Fix building error.
Date: Thu, 23 Dec 2010 15:13:37 +0800 [thread overview]
Message-ID: <4D12F6A1.6040701@cn.fujitsu.com> (raw)
In-Reply-To: <2128862333.62000.1293087724834.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
CAI Qian wrote:
>> However, many people use the LTP to test their own linux system, if those kernel
>> is not support KSM, at least we should make sure they can build
>> successfully.
> In that case, why not use an older version?
But how to choose the older version, it means which LTP is the better one? ^_^
And, maybe a new case is designed to test all versions of linux include the older one.
>
> CAI Qian
>
>
--
Regards
Bian Naimeng
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-12-23 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 6:15 [LTP] [PATCH]Fix building error Bian Naimeng
2010-12-21 6:20 ` Bian Naimeng
2010-12-21 6:39 ` CAI Qian
2010-12-21 7:02 ` Bian Naimeng
2010-12-21 7:11 ` CAI Qian
2010-12-21 7:31 ` Bian Naimeng
2010-12-21 8:05 ` Garrett Cooper
2010-12-23 6:45 ` Bian Naimeng
2010-12-23 7:02 ` CAI Qian
2010-12-23 7:13 ` Bian Naimeng [this message]
2010-12-23 19:25 ` Garrett Cooper
2010-12-27 5:27 ` CAI Qian
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=4D12F6A1.6040701@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=caiqian@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