All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Domenech Goulart <mario@ossystems.com.br>
To: Daiane Angolini <daiane.angolini@freescale.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [Documentation][RFC 3/3] RN: Add the Release Schedule section
Date: Wed, 11 Jun 2014 18:02:59 +0000	[thread overview]
Message-ID: <87wqcnjpd8.fsf@parenteses.org> (raw)
In-Reply-To: <1402508298-5176-3-git-send-email-daiane.angolini@freescale.com> (Daiane Angolini's message of "Wed, 11 Jun 2014 14:38:18 -0300")

Hi Daiane,

On Wed, 11 Jun 2014 14:38:18 -0300 Daiane Angolini <daiane.angolini@freescale.com> wrote:

> Say it is based on Yocto Project.
>
> Please comment on how to point to YP URL.
>
> Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
> ---
>  release-notes/source/introduction.rst | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/release-notes/source/introduction.rst b/release-notes/source/introduction.rst
> index a81fc7d..68015aa 100644
> --- a/release-notes/source/introduction.rst
> +++ b/release-notes/source/introduction.rst
> @@ -4,3 +4,13 @@ Introduction
>  This document has the release notes of the FSL Community BSP |release|
>  which is a communty effort to improve Freescale's
>  processors support in OpenEmbedded and in the Yocto Project.
> +
> +Release Schedule
> +----------------
> +
> +The FSL Communtiy BSP follows the same release schedule from Yocto Project.

I suggest

  The FSL Community BSP follows the same release schedule as
  the Yocto Project's.

If you don't agree with the suggestion, please, note the
s/Communtiy/Community/ typo fix.

> +Since Yocto Project release 1.3 (denzil) meta-fsl-arm, meta-fsl-demos and meta-fsl-arm-extra
> +follow the same *release schedule* and the same *branch naming* from Yocto Project.

s/Yocto Project/the Yocto Project/

> +
> +See the `Yocto Projec Release <https://wiki.yoctoproject.org/wiki/Releases>`_, for details
> +on the Yocto Project.

I suggest 

  See the `Yocto Project Releases <https://wiki.yoctoproject.org/wiki/Releases>`_ document
  for details on the Yocto Project.

(note s/Projec Release/Project Releases/)

I don't know what the `_' character is for in that sentence. I assume it
is a rst syntax, so I've kept it.  If it is noise, please consider
removing it.

Mario
-- 
http://www.ossystems.com.br


  reply	other threads:[~2014-06-11 18:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 17:38 [Documentation][RFC 1/3] RN: Add pointer to kernel linux section Daiane Angolini
2014-06-11 17:38 ` [Documentation][RFC 2/3] RN: Update BSP scope to point external links and Freescale RN Daiane Angolini
2014-06-11 17:51   ` Daiane.Angolini
2014-06-11 18:12   ` Mario Domenech Goulart
2014-06-11 18:17     ` Daiane.Angolini
2014-06-12  6:58       ` zhenhua.luo
2014-06-12 12:58         ` Otavio Salvador
2014-06-12 13:18         ` Daiane.Angolini
2014-06-11 17:38 ` [Documentation][RFC 3/3] RN: Add the Release Schedule section Daiane Angolini
2014-06-11 18:02   ` Mario Domenech Goulart [this message]
2014-06-18 18:16     ` Daiane Angolini

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=87wqcnjpd8.fsf@parenteses.org \
    --to=mario@ossystems.com.br \
    --cc=daiane.angolini@freescale.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.