From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Variable reference (was: Documentation update about machine conf files)
Date: Mon, 24 Aug 2009 17:00:47 +0200 [thread overview]
Message-ID: <4A92AB1F.3060404@dresearch.de> (raw)
In-Reply-To: <200908211344.53306.holger+oe@freyther.de>
>> Would be nice if it is not a glossary only but contains additional info
>> (e.g. exact usage, restrictions, dependencies, examples). This may be
>> realized by references to an own (wiki) page for each variable which needs
>> more than a one liner.
>>
>> What's the community opinion? Should we start such an index in the wiki?
>
> Long time ago, I created conf/documentation.conf. For every variable back then
> we have used VAR[doc] = "Documentation" to describe the semantic of this
> variable. A utility like bitdoc spit out a HTML page...
>
> I would like to see this updated.
It's a good starting point. But it has one drawback: It allows a short one liner docu only. Often it would be great to have some more info, e.g. a list of supported image file system types for IMAGE_FSTYPES.
Steffen
next prev parent reply other threads:[~2009-08-24 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 6:11 Variable reference (was: Documentation update about machine conf files) Steffen Sledz
2009-08-21 11:44 ` Holger Hans Peter Freyther
2009-08-24 15:00 ` Steffen Sledz [this message]
2009-08-25 2:03 ` Holger Hans Peter Freyther
2009-08-25 10:45 ` Steffen Sledz
2009-08-25 12:18 ` Holger Hans Peter Freyther
2009-08-25 14:51 ` Christian Gagneraud
2009-08-26 7:39 ` Steffen Sledz
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=4A92AB1F.3060404@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.