From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@vger.kernel.org
Subject: [ANNOUNCE] LTP Roadmap Released
Date: Thu, 05 Jul 2007 19:42:37 +0530 [thread overview]
Message-ID: <468CFC55.4090702@linux.vnet.ibm.com> (raw)
Hi All,
Sometime back we started retrospection on LTP and the various ways to
make it better. It resulted in critical evaluation of LTP within &
outside LTP users community. It also reflected the various ways on
making it more better and effective. Working in this direction, we have
come up with a road map which we feel will be helpful to the community.
The following wiki pages will throw some light on the same:
* http://ltp.sourceforge.net/wiki/
* http://ltp.sourceforge.net/wikiArchives.php
Your comments on the contents and the goals set will be highly
appreciated. All comments will be published on the above wiki pages.
Regards & Thanks--
Subrata Modak
reply other threads:[~2007-07-05 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=468CFC55.4090702@linux.vnet.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).