From: E Robertson <e.robertson.svg@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New OE user question
Date: Mon, 31 Mar 2008 12:09:23 -0500 [thread overview]
Message-ID: <200803311209.30302.e.robertson.svg@gmail.com> (raw)
In-Reply-To: <f96d234e0803310833g4565e51u2abbc47312c05f07@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
> http://amethyst.openembedded.net/oe/viewmtn/viewmtn.py/branch/changes/org.o
>penembedded.documentation
>
> Patches welcome.
>
> The rest of the documentation is in a Drupal wiki, and can be edited.
> You may need a user account.
>
I've checked out the documentation branch but find myself looking at xml
files. Is their an editor I can use to edit the files so I wouldn't have to
worry about xml syntax?
Their are 9 chapters on the OE website but only 8 in the branch, dit I pull
the correct branch?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2008-03-31 17:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 14:07 New OE user question E Robertson
2008-03-31 15:33 ` Cliff Brake
2008-03-31 16:19 ` E Robertson
2008-03-31 17:12 ` Cliff Brake
2008-03-31 17:09 ` E Robertson [this message]
2008-03-31 17:33 ` Cliff Brake
2008-03-31 15:44 ` Leon Woestenberg
2008-03-31 16:12 ` Koen Kooi
2008-03-31 16:26 ` E Robertson
2008-03-31 16:34 ` Geoffrey Wossum
2008-03-31 17:47 ` Leon Woestenberg
2008-04-01 5:45 ` Ulf Samuelsson
2008-03-31 16:01 ` Geoffrey Wossum
2008-04-01 6:40 ` OE Manual: License change? (was: Re: New OE user question) Marcin Juszkiewicz
2008-04-01 11:00 ` OE Manual: License change? Jeremy Lainé
2008-04-01 13:08 ` Leon Woestenberg
2008-04-01 15:27 ` Marcin Juszkiewicz
2008-04-01 15:54 ` Robert Schuster
2008-04-01 20:48 ` Richard Purdie
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=200803311209.30302.e.robertson.svg@gmail.com \
--to=e.robertson.svg@gmail.com \
--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.