From: Martyn Welch <martyn.welch@gefanuc.com>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: Importing docs directory to org.oe.dev.
Date: Wed, 25 Feb 2009 09:56:59 +0000 [thread overview]
Message-ID: <49A515EB.2060207@gefanuc.com> (raw)
In-Reply-To: <1235492099.27962.62.camel@andromeda>
Michael 'Mickey' Lauer wrote:
> I want to propose importing the documentation into the org.oe.dev
> branch, notably in the docs directly.
>
This is a very sensible suggestion - the docs should reflect the branch in which that exist, the docs for the stable branch will by necessity need to be different from those of devel at times. An example would be the change from ipkg to opkg.
Martyn
--
Martyn Welch MEng MPhil MIET (Principal Software Engineer) T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd, |Registered in England and Wales
Tove Valley Business Park, Towcester, |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB VAT:GB 729849476
next prev parent reply other threads:[~2009-02-25 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 2:18 Documentation/User Manual questions Theodore A. Roth
2009-02-24 14:51 ` Cliff Brake
2009-02-24 16:14 ` RFC: Importing docs directory to org.oe.dev Michael 'Mickey' Lauer
2009-02-24 16:17 ` Michael 'Mickey' Lauer
2009-02-24 16:37 ` Cliff Brake
2009-02-24 16:53 ` Koen Kooi
2009-02-25 9:56 ` Martyn Welch [this message]
2009-02-25 10:00 ` Michael 'Mickey' Lauer
2009-02-25 14:48 ` Documentation/User Manual questions Philip Balister
2009-02-25 16:28 ` Cliff Brake
2009-02-27 22:00 ` Philip Balister
2009-03-02 6:48 ` Sledz, Steffen
2009-03-03 16:40 ` Cliff Brake
2009-03-03 18:05 ` Theodore A. Roth
2009-03-04 6:57 ` Sledz, Steffen
2009-03-03 16:36 ` Cliff Brake
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=49A515EB.2060207@gefanuc.com \
--to=martyn.welch@gefanuc.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.