All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robbie Williamson <robbie@ubuntu.com>
To: subrata@linux.vnet.ibm.com
Cc: ltp-list <ltp-list@lists.sf.net>,
	Mike Frysinger <vapier@gentoo.org>,
	Michael Reed <mreed10@us.ibm.com>, Cai Qian <qcai@redhat.com>,
	Nate Straz <nate@refried.org>,
	"manoj.iyer" <manoj.iyer@canonical.com>
Subject: Re: [LTP] Dead End with LTP Options
Date: Tue, 18 Aug 2009 09:10:01 -0500	[thread overview]
Message-ID: <4A8AB639.8030000@ubuntu.com> (raw)
In-Reply-To: <1250586433.9913.15.camel@subratamodak.linux.ibm.com>

On 08/18/2009 04:07 AM, Subrata Modak wrote:
> Hi,
> 
> We are about to hit the dead end for LTP options with increasing no. of
> options being added to 'runltp' with each passing day. And even with
> line items i have for ltp in 2009 alone, it will easily add up to 3-4
> options.
> 
> Now, this will become a mess in future:
> 
>      1. "./runltp -h" will scroll up and will not show on a single
>         screen,
I really don't see this as a problem, as I'd expect someone running the ltp to
know how to |more....or |less. ;)

>      2. It will be difficult for users to remember all options and their
>         usage as no. of options increase manifold, which is already too
>         much.
Perhaps it's time to create a manpage?

> 
> While there is no doubt that we will keep adding more punch to ltp and
> the way it provisions tests in future, so, the time has come for us to
> adhere to a simpler process which can be easily:
> 
>      1. Used &
>      2. Maintained
> 
> I have no reservations of how it should be implemented, so, would like
> to hear from you on how it can be done best. I would like to see just
> the following command execute LTP as desired by the user:
> 
> ./runltp
> 
> And the remaining choice of providing more options to 'runltp' hidden
> somewhere.
> 
> Regards--
> Subrata
> 
> 


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2009-08-18 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  9:07 [LTP] Dead End with LTP Options Subrata Modak
2009-08-18 10:05 ` Mike Frysinger
2009-08-18 14:10 ` Robbie Williamson [this message]
2009-08-19  0:44 ` manoj.iyer

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=4A8AB639.8030000@ubuntu.com \
    --to=robbie@ubuntu.com \
    --cc=ltp-list@lists.sf.net \
    --cc=manoj.iyer@canonical.com \
    --cc=mreed10@us.ibm.com \
    --cc=nate@refried.org \
    --cc=qcai@redhat.com \
    --cc=subrata@linux.vnet.ibm.com \
    --cc=vapier@gentoo.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.