From: Steven Grunza <steven.grunza@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [RFC] Create a Release Notes document
Date: Mon, 15 Apr 2013 21:03:30 -0400 [thread overview]
Message-ID: <516CA362.3040604@gmail.com> (raw)
In-Reply-To: <CAP9ODKrxzF6LwBOTzwhS-JMixmLXHEcFgyRhXowN+xFdsSDM-w@mail.gmail.com>
On 4/15/2013 9:16 AM, Otavio Salvador wrote:
> Hello,
>
>
> As our community BSP is growing the need for more documentation is
> also getting more important so I’d like to propose the creation of a
> Release Notes document.
>
>
> The idea is it to create it colaboratively, so people who wants to
> help, can contribute to its creation and be an active part of it. My
> proposed strucuture of the document would be the following:
>
>
> SUMARY
>
> Index
> Introduction
> BSP scope
> meta-fsl-arm
> meta-fsl-arm-extra
> Supported machines
> Hardware acceleration
> GPU
> VPU/IPU
> Know issues
> …
>
> What your thoguhts about all this? Do you want to be part of it?
>
> Regards,
>
> --
> Otavio Salvador O.S. Systems
> E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
> Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
Perhaps it's just my extreme newness to git but I would find a section
with directions on how to go from a completely empty directory to a
finished build quite useful. I always seem to have problems with being
on the wrong branch and when I reach out for help I get instructions to
"use the correct branch" but no info on how to switch to the correct
branch. Reading the man pages is important but there are sometimes
things that just can't be figured out from man pages.
next prev parent reply other threads:[~2013-04-16 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 13:16 [RFC] Create a Release Notes document Otavio Salvador
2013-04-16 1:03 ` Steven Grunza [this message]
2013-04-16 13:36 ` RES: " Angolini Daiane-B19406
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=516CA362.3040604@gmail.com \
--to=steven.grunza@gmail.com \
--cc=meta-freescale@yoctoproject.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.