public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Shubham Goyal <shubham@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [ANNOUNCE] The Linux Test Project has been released for JUNE 2012.
Date: Tue, 19 Jun 2012 11:57:16 -0300	[thread overview]
Message-ID: <1340117836.2512.24.camel@freedom> (raw)
In-Reply-To: <4FD9D1DC.9010004@linux.vnet.ibm.com>

On Thu, 2012-06-14 at 17:28 +0530, Shubham Goyal wrote:
> Hi,
> 
> The Linux Test Project test suite has been released for the month of
> JUNE 2012.
> 
> The latest version of the test-suite contains 3000+ tests for the Linux
> OS and can be found at:
> http://ltp.sourceforge.net/,
> Latest happenings in LTP can also be found at:
> http://ltp.sourceforge.net/wiki/,
> http://ltp.sourceforge.net/wikiArchives.php, and,
> IRC: irc.freenode.org #ltp.
> 
> Our web site also contains other information such as:
> - A Linux test tools matrix
> - Technical papers
> - How To's on Linux testing
> - Code coverage analysis tool.

The wiki front page references some pretty old events. Some options that
comes into my mind:

1) Remove the sourceforge site, port the relevant documentation to a
github wiki [1], and move the site to be hosted under the github
infrastructure, ltp.github.com
2) Just heavily clean up and organize the existing sourceforge wiki.

Obviously this is just a suggestion, please don't be mad at me :) I find
useful to keep disciplined and try to keep the online documentation tidy
and up to date (although this is a difficult goal indeed).

[1] It's a wiki repo with text files, that can be in several different
formats, such as reStructuredText

> We would encourage the community to post results to
> ltp-results@lists.sf.net,
> 
> patches, new tests, bugs or comments/questions to ltp-list@lists.sf.net,
> 
> http://sourceforge.net/tracker/?func=add&group_id=3382&atid=103382  (for
> New Bug(s)),
> http://sourceforge.net/tracker/?func=add&group_id=3382&atid=303382  (for
> New Patch(s)),
> http://sourceforge.net/tracker/?func=add&group_id=3382&atid=353382  (for
> New Feature Request(s))
> 
> **Note: Some pending patches will be checked in for next release.
> 
> --Shubham
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

       reply	other threads:[~2012-06-19 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4FD9D1DC.9010004@linux.vnet.ibm.com>
2012-06-19 14:57 ` Lucas Meneghel Rodrigues [this message]
2012-06-19 15:16   ` [LTP] [ANNOUNCE] The Linux Test Project has been released for JUNE 2012 Wanlong Gao
2012-06-19 15:27     ` Lucas Meneghel Rodrigues
2012-06-20  9:13   ` chrubis
     [not found]     ` <1340199221.2424.4.camel@freedom>
2012-06-20 12:57       ` 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=1340117836.2512.24.camel@freedom \
    --to=lmr@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=shubham@linux.vnet.ibm.com \
    /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