All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation update about machine conf files
Date: Tue, 18 Aug 2009 10:42:37 +0200	[thread overview]
Message-ID: <4A8A697D.9080105@dresearch.de> (raw)
In-Reply-To: <4A89A884.6030904@techworks.ie>

Christian Gagneraud schrieb:
> I'm willing to update the manual, especially the section "Adding a new
> Machine". I would like to update the list or required variables (if it
> needs to) and add a list of optional but useful variables (see my
> previous post as well).
> But i'm wondering if the the file conf/documentation.conf is a better
> place and/or a new conf/machine/machine.conf.sample could be written in
> the same way as the conf/local.conf.sample one.
> ...

I would be really happy about an index of *all* variables usable in the recipes together with a desciption or a reference to it. I would prefer such an index in the wiki, but manual or documentation.conf would be fine too.

Steffen





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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 18:59 Documentation update about machine conf files Christian Gagneraud
2009-08-18  8:42 ` Steffen Sledz [this message]
2009-08-20 19:25   ` Marcin Juszkiewicz

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=4A8A697D.9080105@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-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.