All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: docs: how to spell "bitbake", and docbook semantic markup for user input
Date: Thu, 14 Jul 2011 10:28:02 +0100	[thread overview]
Message-ID: <1310635682.20015.1124.camel@rex> (raw)
In-Reply-To: <4E1E627B.80801@linux.intel.com>

On Wed, 2011-07-13 at 20:28 -0700, Darren Hart wrote:
> 
> On 07/13/2011 03:48 PM, Joshua Lock wrote:
> > On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:
> >> just perusing the documentation in my typically pedantic fashion and
> >> a couple questions about style.  first, is the proper spelling
> >> "Bitbake" or "BitBake" since the doc source seems to bounce back and
> >> forth and it really should be consistent.
> > 
> > I believe it's the latter, at least that's what I've always use.
> > 
> 
> Agreed:
> 
> The man page:
> BitBake - simple tool for the execution of tasks
> 
> The user manual:
> BitBake User Manual
> 
> Those seem like the two lines of documentation that are most likely to
> be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.

I think we've been leaning towards BitBake for a while.

Cheers,

Richard




  reply	other threads:[~2011-07-14  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 10:57 docs: how to spell "bitbake", and docbook semantic markup for user input Robert P. J. Day
2011-07-13 22:48 ` Joshua Lock
2011-07-14  3:28   ` Darren Hart
2011-07-14  9:28     ` Richard Purdie [this message]
2011-07-14  9:46     ` Robert P. J. Day
2011-07-14 10:01       ` Richard Purdie
2011-07-14 14:04         ` Rifenbark, Scott M
2011-07-14 14:29           ` Robert P. J. Day
2011-07-14 14:31             ` Rifenbark, Scott M
2011-07-14  9:31 ` Richard Purdie

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=1310635682.20015.1124.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dvhart@linux.intel.com \
    --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.