All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rifenbark, Scott M" <scott.m.rifenbark@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: is there a TODO/issues list for bitbake user manual enhancements?
Date: Thu, 26 Jun 2014 22:05:22 -0700	[thread overview]
Message-ID: <53ACFB92.7070007@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1406201322310.28485@localhost>

Robert,

The best way to track this stuff is to open a bug on it in Bugzilla 
(https://bugzilla.yoctoproject.org/).  Assign the bug to me and note 
these specific variables.

Thanks,
Scott

On 6/20/2014 10:26 AM, Robert P. J. Day wrote:
>    is there anywhere to track proposed changes to the bitbake user
> manual? one of the things i've already noted is that the variable
> glossary is somewhat incomplete. for example, at the very least, it
> should include the following variables that are explicitly set in
> bitbake's own bitbake.conf file:
>
>   CVSDIR
>   DEPLOY_DIR
>   DEPLOY_DIR_IMAGE
>   FILE_DIRNAME
>   GITDIR
>   IMAGE_CMD
>   IMAGE_ROOTFS
>   P
>   S
>   SVNDIR
>   TARGET_ARCH
>   TMPDIR
>   WORKDIR
>
> is there a list to add these to? or is most of the effort these days
> being invested in the yocto version of the ref manual?

I spend time in the BitBake manual as needed.  BTW - your patches to it 
have been applied.  They might not be in the BitBake repo yet but they 
are applied and in my contrib area.  And, of course, you can see them in 
the "latest" version of the manual.

>
> rday
>



  reply	other threads:[~2014-06-27  5:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 17:26 is there a TODO/issues list for bitbake user manual enhancements? Robert P. J. Day
2014-06-27  5:05 ` Rifenbark, Scott M [this message]
2014-08-06 16:51 ` Paul Eggleton

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=53ACFB92.7070007@linux.intel.com \
    --to=scott.m.rifenbark@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.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.