From: Michael 'Mickey' Lauer <mlauer@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Importing docs directory to org.oe.dev.
Date: Tue, 24 Feb 2009 17:17:41 +0100 [thread overview]
Message-ID: <1235492261.27962.63.camel@andromeda> (raw)
In-Reply-To: <1235492099.27962.62.camel@andromeda>
Am Dienstag, den 24.02.2009, 17:14 +0100 schrieb Michael 'Mickey' Lauer:
> I want to propose importing the documentation into the org.oe.dev
> branch, notably in the docs directly.
s/directly/directory/.
--
:M:
next prev parent reply other threads:[~2009-02-24 16:20 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 [this message]
2009-02-24 16:37 ` Cliff Brake
2009-02-24 16:53 ` Koen Kooi
2009-02-25 9:56 ` Martyn Welch
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=1235492261.27962.63.camel@andromeda \
--to=mlauer@vanille-media.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox