From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] m28evk: Move README file inside board directory
Date: Fri, 3 May 2013 22:47:44 +0200 [thread overview]
Message-ID: <201305032247.45024.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5Dp9DamSk++=bihEaKWUOeujqN8qoDhdGJc81zfYBH4eg@mail.gmail.com>
Dear Fabio Estevam,
> On Fri, May 3, 2013 at 4:54 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Fabio Estevam,
> >
> >> From: Fabio Estevam <fabio.estevam@freescale.com>
> >>
> >> Board specific READMEs should be located inside the respective board
> >> directory.
> >
> > Where did you find this rule?
>
> Here:
>
> commit 702e6014f15b307f144fa03ecaf83a8446c6802a
> Author: Wolfgang Denk <wd@denx.de>
> Date: Sun Apr 29 23:57:39 2012 +0000
I see, thanks.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-05-03 20:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 18:07 [U-Boot] [PATCH 1/6] README: mx28_common: Keep the text within 80 columns Fabio Estevam
2013-05-03 18:07 ` [U-Boot] [PATCH 2/6] README: mx28_common: Do not hardcode the SSP port Fabio Estevam
2013-05-03 19:52 ` Marek Vasut
2013-05-03 20:42 ` Fabio Estevam
2013-05-03 20:47 ` Marek Vasut
2013-06-26 15:42 ` Stefano Babic
2013-05-03 18:07 ` [U-Boot] [PATCH 3/6] README: mx28_common: Fix structure of sentence Fabio Estevam
2013-06-26 15:42 ` Stefano Babic
2013-05-03 18:08 ` [U-Boot] [PATCH 4/6] README: mxs: Introduce README.mxs Fabio Estevam
2013-05-03 19:54 ` Marek Vasut
2013-06-26 15:42 ` Stefano Babic
2013-05-03 18:08 ` [U-Boot] [PATCH 5/6] mx28evk: Move README file inside board directory Fabio Estevam
2013-06-26 15:43 ` Stefano Babic
2013-06-26 15:46 ` Otavio Salvador
2013-06-26 19:57 ` Marek Vasut
2013-05-03 18:08 ` [U-Boot] [PATCH 6/6] m28evk: " Fabio Estevam
2013-05-03 19:54 ` Marek Vasut
2013-05-03 20:23 ` Fabio Estevam
2013-05-03 20:47 ` Marek Vasut [this message]
2013-06-26 15:44 ` Stefano Babic
2013-06-26 15:43 ` [U-Boot] [PATCH 1/6] README: mx28_common: Keep the text within 80 columns Stefano Babic
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=201305032247.45024.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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