From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation problems
Date: Mon, 28 Nov 2011 08:36:30 -0500 [thread overview]
Message-ID: <4ED38E5E.9060201@balister.org> (raw)
In-Reply-To: <4ED38DA1.8060802@balister.org>
On 11/28/2011 08:33 AM, Philip Balister wrote:
> On 11/28/2011 06:16 AM, Otavio Salvador wrote:
>> On Mon, Nov 28, 2011 at 09:07, Richard Purdie <
>> richard.purdie@linuxfoundation.org> wrote:
>>
>>> Rather than fork off the Yocto docs for OE's needs, it would be nice to
>>> see if there was a way we could share the documentation.
>>>
>>
>> I fully agree with that.
>>
>> The work would be much easier if all that could be shared.
>>
>> AFAIK, using docbook it is possible to use macros to expand for branding
>> and also conditional to output text so this could be done in a single
>> repository.
>>
>
> We need to be really careful how all the pieces get branded. There is
> way too much confusion already, without referring people to the "Yocto
> Instructions" to use OE-core + layers.
Just to be really clear .....
Also, not I am not opposed to a unified documentation set, just that it
is clear to people what things are called.
Philip
next prev parent reply other threads:[~2011-11-28 13:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 2:40 Documentation problems Tom Rini
2011-11-27 9:58 ` [RFC] Documentation problems and future plans Paul Menzel
2011-11-27 15:51 ` Chris Larson
2011-11-27 14:29 ` Documentation problems Paul Eggleton
2011-11-27 15:53 ` Chris Larson
2011-11-27 16:58 ` Frans Meulenbroeks
2011-11-27 17:06 ` Paul Eggleton
2011-11-27 18:38 ` Paul Menzel
2011-11-27 18:56 ` Paul Eggleton
2011-11-27 19:06 ` Paul Menzel
2011-11-27 21:49 ` Frans Meulenbroeks
2011-11-27 22:00 ` Paul Menzel
2011-11-27 15:44 ` Koen Kooi
2011-11-28 5:11 ` Tom Rini
2011-11-28 6:36 ` Chris Verges
2011-11-28 9:23 ` Koen Kooi
2011-11-28 12:19 ` Denis 'GNUtoo' Carikli
2011-11-28 13:40 ` Paul Eggleton
2011-11-28 14:40 ` Samuel Stirtzel
2011-11-28 10:30 ` Phil Blundell
2011-11-28 11:07 ` Richard Purdie
2011-11-28 11:16 ` Otavio Salvador
2011-11-28 13:33 ` Philip Balister
2011-11-28 13:36 ` Philip Balister [this message]
2011-11-28 14:06 ` Koen Kooi
2011-11-28 18:02 ` Bernhard Guillon
2011-11-28 21:13 ` Tom Rini
2011-11-29 8:24 ` Frans Meulenbroeks
2011-11-29 20:17 ` Khem Raj
2011-11-29 21:46 ` Frans Meulenbroeks
2011-11-29 23:37 ` Tom Rini
2011-11-30 7:06 ` Frans Meulenbroeks
2011-11-28 17:44 ` Bernhard Guillon
2011-12-07 5:01 ` Bill Traynor
2011-12-07 22:17 ` Khem Raj
2011-11-30 15:49 ` Rainer Koenig
2011-11-30 17:06 ` Koen Kooi
2011-11-30 17:32 ` McClintock Matthew-B29882
2011-11-30 18:46 ` Paul Menzel
-- strict thread matches above, loose matches on Subject: below --
2009-09-20 17:58 Bruce Korb
2009-09-20 18:24 ` Matthieu Moy
2009-09-20 18:37 ` Bruce Korb
2009-09-20 18:45 ` Matthieu Moy
2009-09-20 20:52 ` Andreas Schwab
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=4ED38E5E.9060201@balister.org \
--to=philip@balister.org \
--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.