Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch sma/doc-update
Date: Fri, 18 Oct 2013 22:31:24 +0200	[thread overview]
Message-ID: <cover.1382127504.git.s.martin49@gmail.com> (raw)

All,


Another round for the manual update patch series.
This time, I also integrate the pending patches from Thomas DS.

BTW, can someone (who has enough patchwork privileges) mark the
following patch as superseded:
http://patchwork.ozlabs.org/patch/214943/


Yours,

--
Samuel


The following changes since commit f87f067c027261eb8c0ac8ad120fe845570aaae3:

  ngrep: add license information (2013-10-15 15:13:28 +0200)

are available in the git repository at:

  git at github.com:tSed/buildroot.git sma/doc-update

for you to fetch changes up to b67f14903e6e33f2790ff7ee8c82c658f8c12b01:

  board: add warning to readme files explaining how to flash the target (2013-10-18 21:34:54 +0200)

----------------------------------------------------------------
Samuel Martin (10):
      support: trivial fixes (typos and minor rewording) in gen-manual-lists.py
      manual: move the manual rsync directory under $(O)/build/
      manual: developer-guide.txt: cleanup non-existing source
      manual: introduction.txt: enhance Buildroot presentation
      manual: get-involved.txt: fix event order
      manual: update get-involved section
      manual: rework Deploying images chapter
      manual: customize-toolchain.txt: update internal backend section
      manual: faq-troubleshooting.txt: add tips to avoid toolchain build
      board: add warning to readme files explaining how to flash the target

Thomas De Schampheleire (2):
      manual generation: check dependencies first
      manual generation: rename manual-txt into manual-text

 Makefile                                    |   4 +-
 board/avnet/s6lx9_microboard/readme.txt     |  10 +
 board/freescale/mpc8315erdb/readme.txt      |   8 +
 board/freescale/p1010rdb/readme.txt         |   8 +
 board/telit/evk-pro3/readme.txt             |   9 +
 docs/manual/beyond-buildroot.txt            |  41 ----
 docs/manual/customize-toolchain.txt         |  13 +-
 docs/manual/deploying-images.txt            | 291 ++++++++++++++++++++++++++++
 docs/manual/developer-guide.txt             |   2 -
 docs/manual/faq-troubleshooting.txt         |  67 +++++++
 docs/manual/get-involved.txt                | 164 +++++++++++++++-
 docs/manual/introduction.txt                |  45 +++++
 docs/manual/make-tips.txt                   |   3 +-
 docs/manual/manual.mk                       |  47 ++++-
 docs/manual/manual.txt                      |   4 +-
 docs/manual/prerequisite.txt                |   5 +-
 docs/manual/using.txt                       |   3 +-
 support/dependencies/check-host-asciidoc.sh |  36 ++++
 support/scripts/gen-manual-lists.py         |   9 +-
 19 files changed, 691 insertions(+), 78 deletions(-)
 delete mode 100644 docs/manual/beyond-buildroot.txt
 create mode 100644 docs/manual/deploying-images.txt
 create mode 100755 support/dependencies/check-host-asciidoc.sh

             reply	other threads:[~2013-10-18 20:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 20:31 Samuel Martin [this message]
2013-10-18 20:31 ` [Buildroot] [PATCH 01/12] manual generation: check dependencies first Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 02/12] manual generation: rename manual-txt into manual-text Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 03/12] support: trivial fixes (typos and minor rewording) in gen-manual-lists.py Samuel Martin
2013-10-20  7:32   ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 04/12] manual: move the manual rsync directory under $(O)/build/ Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 05/12] manual: developer-guide.txt: cleanup non-existing source Samuel Martin
2013-10-20 19:14   ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 06/12] manual: introduction.txt: enhance Buildroot presentation Samuel Martin
2013-11-01 16:17   ` Thomas Petazzoni
2013-10-18 20:31 ` [Buildroot] [PATCH 07/12] manual: get-involved.txt: fix event order Samuel Martin
2013-11-01 16:18   ` Thomas Petazzoni
2013-11-02 14:54     ` Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 08/12] manual: update get-involved section Samuel Martin
2013-11-01 16:19   ` Thomas Petazzoni
2013-11-02 15:12     ` Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 09/12] manual: rework Deploying images chapter Samuel Martin
2013-11-01 16:36   ` Thomas Petazzoni
2013-11-06 12:54   ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 10/12] manual: customize-toolchain.txt: update internal backend section Samuel Martin
2013-10-21  6:25   ` Thomas De Schampheleire
2013-10-18 20:31 ` [Buildroot] [PATCH 11/12] manual: faq-troubleshooting.txt: add tips to avoid toolchain build Samuel Martin
2013-10-18 20:31 ` [Buildroot] [PATCH 12/12] board: add warning to readme files explaining how to flash the target Samuel Martin
2013-10-22 15:13   ` Thomas Petazzoni
2013-11-01 16:12 ` [Buildroot] [pull request] Pull request for branch sma/doc-update Thomas Petazzoni
2013-11-01 21:08   ` Samuel Martin
  -- strict thread matches above, loose matches on Subject: below --
2013-10-05 19:49 Samuel Martin

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=cover.1382127504.git.s.martin49@gmail.com \
    --to=s.martin49@gmail.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