From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request v5] Pull request for branch for-master/doc
Date: Thu, 21 Mar 2013 22:04:31 +0100 [thread overview]
Message-ID: <cover.1363899518.git.s.martin49@gmail.com> (raw)
Hello All!
Another (and hopefully the last) round of the doc series...
Changes v4 -> v5:
- Kconfiglib python module eventually gets embedded in the BR source tree;
- Manual generation date now appears in the manual.
The following changes since commit 1f721a2f009393c29c6554f643f15f80a8dc5443:
xinetd: follow the convention for patch location (2013-03-20 23:28:27 +0100)
are available in the git repository at:
git://github.com/tSed/buildroot.git for-master/doc
for you to fetch changes up to 8be5fe492147513305626d9665d4119c548be11e:
manual: update generated lists (2013-03-21 21:33:12 +0100)
----------------------------------------------------------------
Samuel Martin (7):
manual: add manual generation date/git revision in the manual text
support: add kconfiglib python module
support/scripts: add gen-manual-lists.py
manual: cleanup appendix.txt
manual: add a make target 'manual-update-lists'
Makefile: add to the release target a warning about the manual updates.
manual: update generated lists
Makefile | 2 +
docs/manual/appendix.txt | 29 +-
docs/manual/deprecated-list.txt | 77 +-
docs/manual/host-package-list.txt | 22 +
docs/manual/manual.mk | 10 +-
docs/manual/manual.txt | 3 +
docs/manual/package-list.txt | 950 +++++++++
docs/manual/pkg-list.txt | 870 --------
support/scripts/gen-manual-lists.py | 348 ++++
support/scripts/kconfiglib.py | 3772 +++++++++++++++++++++++++++++++++++
support/scripts/readme | 30 +
11 files changed, 5189 insertions(+), 924 deletions(-)
create mode 100644 docs/manual/host-package-list.txt
create mode 100644 docs/manual/package-list.txt
delete mode 100644 docs/manual/pkg-list.txt
create mode 100755 support/scripts/gen-manual-lists.py
create mode 100644 support/scripts/kconfiglib.py
create mode 100644 support/scripts/readme
Yours,
Samuel
--
next reply other threads:[~2013-03-21 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 21:04 Samuel Martin [this message]
2013-03-21 21:04 ` [Buildroot] [PATCH 1/7] manual: add manual generation date/git revision in the manual text Samuel Martin
2013-03-21 21:04 ` [Buildroot] [PATCH 2/7] support: add kconfiglib python module Samuel Martin
2013-03-21 21:04 ` [Buildroot] [PATCH 3/7] support/scripts: add gen-manual-lists.py Samuel Martin
2013-03-21 21:04 ` [Buildroot] [PATCH 4/7] manual: cleanup appendix.txt Samuel Martin
2013-03-21 21:04 ` [Buildroot] [PATCH 5/7] manual: add a make target 'manual-update-lists' Samuel Martin
2013-03-21 21:04 ` [Buildroot] [PATCH 6/7] Makefile: add to the release target a warning about the manual updates Samuel Martin
2013-03-21 21:04 ` [Buildroot] [PATCH 7/7] manual: update generated lists Samuel Martin
2013-03-22 8:23 ` Thomas Petazzoni
2013-03-23 17:03 ` [Buildroot] [pull request v5] Pull request for branch for-master/doc Thomas Petazzoni
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.1363899518.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