From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch doc-updates
Date: Sun, 30 Jan 2011 15:37:44 +0100 [thread overview]
Message-ID: <cover.1296398261.git.thomas.petazzoni@free-electrons.com> (raw)
The following changes since commit 0fa46e59db087478b4844b2358a496eacdef7569:
Peter Korsgaard (1):
lzo: build shared library for host and target
are available in the git repository at:
git://git.busybox.net/~tpetazzoni/git/buildroot doc-updates
Thomas Petazzoni (6):
Explain why we don't support ELDK toolchains.
Update documentation about external toolchain
Remove more or less inexact option concerning custom target skeleton
Use <code> instead of <pre> to improve formatting
Do not mention toolchain/uClibc/uClibc.config-locale
documentation: mention we can't use the distro toolchain as external
docs/buildroot.html | 113 +++++++++++++++++++++++++++++++++++---------------
1 files changed, 79 insertions(+), 34 deletions(-)
Thanks,
--
Thomas Petazzoni
next reply other threads:[~2011-01-30 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 14:37 Thomas Petazzoni [this message]
2011-01-30 14:37 ` [Buildroot] [PATCH 1/6] Explain why we don't support ELDK toolchains Thomas Petazzoni
2011-01-30 14:37 ` [Buildroot] [PATCH 2/6] Update documentation about external toolchain Thomas Petazzoni
2011-01-30 14:37 ` [Buildroot] [PATCH 3/6] Remove more or less inexact option concerning custom target skeleton Thomas Petazzoni
2011-01-30 14:37 ` [Buildroot] [PATCH 4/6] Use <code> instead of <pre> to improve formatting Thomas Petazzoni
2011-01-30 14:37 ` [Buildroot] [PATCH 5/6] Do not mention toolchain/uClibc/uClibc.config-locale Thomas Petazzoni
2011-01-30 19:11 ` Peter Korsgaard
2011-01-30 14:37 ` [Buildroot] [PATCH 6/6] documentation: mention we can't use the distro toolchain as external Thomas Petazzoni
2011-01-30 19:14 ` [Buildroot] [pull request] Pull request for branch doc-updates Peter Korsgaard
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.1296398261.git.thomas.petazzoni@free-electrons.com \
--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