From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: wiki development pages
Date: Sun, 20 Jul 2008 13:39:02 -0300 [thread overview]
Message-ID: <8763r0fr2x.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <8c7950360807200913q20f35f91iac45d216665738d9@mail.gmail.com> (Shane Volpe's message of "Sun\, 20 Jul 2008 12\:13\:36 -0400")
"Shane Volpe" <shanevolpe@gmail.com> writes:
> I'm going to start some wiki pages on the OE wiki that will be very
> rough and under heavy development. Should I make a wiki section
> called "Pages under heavy development" or just put a disclaimer at the
> top of the pages saying it is under development and probably contains
> incorrect data?
>
> The page I'm creating is detailing how I used OE in a commercial
> product and my approaches in version control, build repeatability and
> generally integrating into my company's design process and
> productization. I'm sure my approaches were not always optimal so I
> hope after I have my approaches documented that others will give
> feedback so we can make a nice wiki on how to use OE in a commercial
> design process.
> Regards,
> Shane
Where you'll put the links to those pages?
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
next prev parent reply other threads:[~2008-07-20 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 16:13 wiki development pages Shane Volpe
2008-07-20 16:39 ` Otavio Salvador [this message]
2008-07-20 17:24 ` Rolf Leggewie
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=8763r0fr2x.fsf@neumann.lab.ossystems.com.br \
--to=otavio@debian.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.