From: tpetazzoni at uclibc.org <tpetazzoni@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/docs
Date: Mon, 15 Dec 2008 14:14:02 -0800 (PST) [thread overview]
Message-ID: <20081215221402.4C8E93C6F0@busybox.net> (raw)
Author: tpetazzoni
Date: 2008-12-15 14:14:02 -0800 (Mon, 15 Dec 2008)
New Revision: 24427
Log:
Mention another important benefit of Buildroot.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Modified:
trunk/buildroot/docs/buildroot.html
Changeset:
Modified: trunk/buildroot/docs/buildroot.html
===================================================================
--- trunk/buildroot/docs/buildroot.html 2008-12-15 22:07:38 UTC (rev 24426)
+++ trunk/buildroot/docs/buildroot.html 2008-12-15 22:14:02 UTC (rev 24427)
@@ -108,6 +108,12 @@
each <code>gcc</code> and <code>binutils</code> version to make them work
on most architectures. </p>
+ <p>Moreover, Buildroot provides an infrastructure for reproducing
+ the build process of your embedded root filesystem. Being able to
+ reproduce the build process will be useful when a component needs
+ to be patched or updated, or when another person is supposed to
+ take over the project.</p>
+
<h2><a name="download" id="download"></a>Obtaining Buildroot</h2>
<p>Buildroot is available as daily SVN snapshots or directly using
next reply other threads:[~2008-12-15 22:14 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 22:14 tpetazzoni at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-02 10:09 [Buildroot] svn commit: trunk/buildroot/docs jacmet at uclibc.org
2009-03-02 8:34 jacmet at uclibc.org
2009-02-12 9:33 jacmet at uclibc.org
2009-02-09 16:44 jacmet at uclibc.org
2009-01-31 23:02 jacmet at uclibc.org
2009-01-26 20:26 ulf at uclibc.org
2009-01-23 21:06 jacmet at uclibc.org
2009-01-16 19:45 jacmet at uclibc.org
2009-01-16 21:02 ` Markus Heidelberg
2009-01-16 19:45 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-06 16:30 ulf at uclibc.org
2009-01-06 16:34 ` Peter Korsgaard
2008-12-18 0:48 root at uclibc.org
2008-12-16 9:00 jacmet at uclibc.org
2008-12-15 22:35 tpetazzoni at uclibc.org
2008-12-15 22:44 ` Thomas Petazzoni
2008-12-16 9:03 ` Peter Korsgaard
2008-12-16 9:00 ` Peter Korsgaard
2008-12-08 8:15 jacmet at uclibc.org
2008-10-14 16:20 aldot at uclibc.org
2008-10-18 6:58 ` Peter Korsgaard
2008-10-06 9:11 jacmet at uclibc.org
2008-06-23 13:40 jacmet at uclibc.org
2008-03-13 17:16 ninevoltz at uclibc.org
2008-03-13 18:25 ` Peter Korsgaard
2007-09-27 21:32 aldot at uclibc.org
2007-09-19 9:08 aldot at uclibc.org
2007-09-02 17:44 aldot at uclibc.org
2007-08-24 5:28 ulf at uclibc.org
2007-08-16 21:54 ulf at uclibc.org
2007-08-12 23:26 ulf at uclibc.org
2007-08-11 21:58 ulf at uclibc.org
2007-08-01 8:11 ulf at uclibc.org
2007-07-12 17:04 ulf at uclibc.org
2007-07-12 16:53 ulf at uclibc.org
2007-07-12 14:46 ulf at uclibc.org
2007-07-12 14:43 ulf at uclibc.org
2007-07-12 15:07 ` Bernhard Fischer
2007-06-21 16:58 aldot at uclibc.org
2007-03-13 12:59 aldot at uclibc.org
2007-01-21 21:49 aldot at uclibc.org
2007-01-19 19:28 aldot at uclibc.org
2007-01-19 19:21 aldot at uclibc.org
2007-01-19 19:20 aldot at uclibc.org
2007-01-19 13:32 aldot at uclibc.org
2007-01-19 12:35 aldot at uclibc.org
2007-01-19 11:00 aldot at uclibc.org
2007-01-19 10:57 aldot at uclibc.org
2007-01-19 9:47 aldot at uclibc.org
2007-01-19 9:24 aldot at uclibc.org
2007-01-17 10:07 aldot at uclibc.org
2006-12-22 12:11 aldot at uclibc.org
2006-11-05 11:21 aldot at uclibc.org
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=20081215221402.4C8E93C6F0@busybox.net \
--to=tpetazzoni@uclibc.org \
--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