Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Documentation/User Manual questions
Date: Fri, 27 Feb 2009 17:00:11 -0500	[thread overview]
Message-ID: <49A8626B.8020209@balister.org> (raw)
In-Reply-To: <f96d234e0902250828x6e72a8b6kc0a4285125f27b0e@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

Cliff Brake wrote:
> On Wed, Feb 25, 2009 at 9:48 AM, Philip Balister <philip@balister.org> wrote:
>> Cliff Brake wrote:
>>> On Fri, Feb 20, 2009 at 9:18 PM, Theodore A. Roth <taroth@gmail.com>
>>> wrote:
>>>
>>>> 2: Was the documentation branch really last updated on May 9, 2008? Is
>>>> there a newer branch I have not yet discovered?
>>> Yes, this is likely correct.  Documentation is not OE's strong point.
>>> But the combination of various docs available cover things pretty
>>> well:
>>>
>>> http://wiki.openembedded.net/index.php/Documentation
>> I notice you keep copies of the manual on your website. Last week Koen
>> suggested we add docs.openembedded.org to DNS. Would it make sense to go
>> ahead and add this address and use it for "static" copies of documentation?
> 
> I have a script that automatically updates the docs and rsyncs them to
> my web site.  I can adjust that as soon as docs.oe.org comes on line.
> Given the reliability of OE infrastructure in the past, it was just a
> lot easier to use my own server, but it seems like things are
> stabilizing now.

docs.openembedded.org is working now. Koen put a copy of the manual up 
there, but I suspect that long term other documents may also belong 
there. I'm not sure who has access to that part of amethyst/ Cliff, Koen 
and others, can you work out the details of keeping this up to date?

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-02-27 22:03 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
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 [this message]
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=49A8626B.8020209@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox