From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] docs: Move README file to root
Date: Sun, 2 Mar 2014 21:41:17 +0100 [thread overview]
Message-ID: <20140302214117.4ba15844@skate> (raw)
In-Reply-To: <1393784504-11327-2-git-send-email-maxime.hadjinlian@gmail.com>
Dear Maxime Hadjinlian,
On Sun, 2 Mar 2014 19:21:41 +0100, Maxime Hadjinlian wrote:
> Move the README file from the subdirectory doc to the root.
>
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
> docs/README => README | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename docs/README => README (100%)
But isn't this README completely crappy as a general presentation of
Buildroot? Shouldn't it be replaced by a better README that contains
some more relevant details?
Of course, I'll take your patch as is, hoping that someone will take on
the job of writing a better README :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-02 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 18:21 [Buildroot] [PATCH 0/4] Brand new website Maxime Hadjinlian
2014-03-02 18:21 ` [Buildroot] [PATCH 1/4] docs: Move README file to root Maxime Hadjinlian
2014-03-02 20:41 ` Thomas Petazzoni [this message]
2014-03-02 22:54 ` Maxime Hadjinlian
2014-03-02 18:21 ` [Buildroot] [PATCH 2/4] website: Add Bootstrap and JQuery framework Maxime Hadjinlian
2014-03-02 18:21 ` [Buildroot] [PATCH 3/4] website: Add Buildroot javascript Maxime Hadjinlian
2014-03-02 18:21 ` [Buildroot] [PATCH 4/4] website: new website ! Maxime Hadjinlian
2014-03-03 10:41 ` Thomas De Schampheleire
2014-03-02 20:38 ` [Buildroot] [PATCH 0/4] Brand new website Thomas De Schampheleire
2014-03-02 20:40 ` Thomas Petazzoni
2014-03-02 22:55 ` Maxime Hadjinlian
2014-03-03 7:53 ` Thomas Petazzoni
2014-03-03 11:12 ` Thomas De Schampheleire
2014-03-03 20:52 ` Thomas Petazzoni
2014-03-03 20:54 ` Thomas De Schampheleire
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=20140302214117.4ba15844@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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