From: Daiane Angolini <daiane.angolini@freescale.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [fsl-community-base][PATCH] README: Add all missing boards
Date: Tue, 15 Oct 2013 14:05:52 -0300 [thread overview]
Message-ID: <525D75F0.60107@freescale.com> (raw)
In-Reply-To: <CAP9ODKqe-zOx=t-Sw2kykCqvLoasu-Shu1Q_o5w6pVcD7DOSWA@mail.gmail.com>
On 10/15/2013 01:35 PM, Otavio Salvador wrote:
> Hello Daiane,
>
> On Tue, Oct 15, 2013 at 12:22 PM, Daiane Angolini
> <daiane.angolini@freescale.com> wrote:
>> Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
>
> comments below ...
>
>> ---
>> README | 47 +++++++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 45 insertions(+), 2 deletions(-)
>>
>
> First, thank you for taking the time to prepare this. However I think
> this is wrong...
>
> When we made this README we had no Release Notes at that time. Since
> this we made a document which provides this information and also way
> more hence it is bad to duplicate all this. I think we ought to point
> to the Release Notes and remove the list of supported boards from the
> README file..
>
> What you think?
I think I agree. When I decided to work on this patch it was the plan B.
Do you have the link for:
* Release Notes for Dora
* Release Notes for master
What is the procedure when a new board was included?
--
Daiane
next prev parent reply other threads:[~2013-10-15 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 15:22 [fsl-community-base][PATCH] README: Add all missing boards Daiane Angolini
2013-10-15 16:35 ` Otavio Salvador
2013-10-15 17:05 ` Daiane Angolini [this message]
2013-10-15 17:55 ` Otavio Salvador
2013-10-15 18:12 ` Daiane Angolini
2013-10-15 18:41 ` Otavio Salvador
2013-10-15 19:39 ` [RFC] Dora Release Notes review 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=525D75F0.60107@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.