All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: are there more yocto-bsp commands other than "create" and "list"?
Date: Wed, 04 Apr 2012 15:56:46 -0500	[thread overview]
Message-ID: <1333573006.2011.12.camel@elnicho> (raw)
In-Reply-To: <alpine.DEB.2.02.1204041614430.11031@oneiric>

On Wed, 2012-04-04 at 16:16 -0400, Robert P. J. Day wrote:
> help for yocto-bsp reads:
> 
>  The most commonly used 'yocto-bsp' commands are:
>     create            Create a new Yocto BSP
>     list              List available values for options and BSP properties
> 
> but from the script:
> 
> subcommands = {
>     "create": [yocto_bsp_create_subcommand,
>                yocto_bsp_create_usage,
>                yocto_bsp_create_help],
>     "list":   [yocto_bsp_list_subcommand,
>                yocto_bsp_list_usage,
>                yocto_bsp_list_help],
> }
> 
>   so it's not so much they're the most common commands, aren't they
> the *only* commands?  or am i misreading something?
> 

At the moment, they are the only commands, and I guess therefore also
the most commonly used.

The interface is modeled after git and perf, which both use the same
text.  I suppose that to avoid being misleading, we should replace 'most
commonly' with 'available', also since I also don't envision adding any
'rare' commands...

Tom

> rday
> 




  reply	other threads:[~2012-04-04 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 20:16 are there more yocto-bsp commands other than "create" and "list"? Robert P. J. Day
2012-04-04 20:56 ` Tom Zanussi [this message]
2012-04-04 21:10   ` Robert P. J. Day

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=1333573006.2011.12.camel@elnicho \
    --to=tom.zanussi@intel.com \
    --cc=rpjday@crashcourse.ca \
    --cc=yocto@yoctoproject.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.