Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel MARTIN <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] docs/buildroot.html: cleanup trailing whitespaces
Date: Sun, 18 Mar 2012 09:53:59 +0100	[thread overview]
Message-ID: <1332060843-2786-2-git-send-email-s.martin49@gmail.com> (raw)
In-Reply-To: <1332060843-2786-1-git-send-email-s.martin49@gmail.com>


Signed-off-by: Samuel MARTIN <s.martin49@gmail.com>
---
 docs/buildroot.html |   24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/buildroot.html b/docs/buildroot.html
index ddfb20a..28aefe4 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -39,22 +39,22 @@
 
     <h2 id="about">About Buildroot</h2>
 
-    <p>Buildroot is a set of Makefiles and patches that allows you to easily 
-    generate a cross-compilation toolchain, a root filesystem and a Linux 
-    kernel image for your target. Buildroot can be used for one, two or all 
+    <p>Buildroot is a set of Makefiles and patches that allows you to easily
+    generate a cross-compilation toolchain, a root filesystem and a Linux
+    kernel image for your target. Buildroot can be used for one, two or all
     of these options, independently.</p>
 
-    <p>Buildroot is useful mainly for people working with embedded systems. 
-    Embedded systems often use processors that are not the regular x86 
-    processors everyone is used to having in his PC. They can be PowerPC 
+    <p>Buildroot is useful mainly for people working with embedded systems.
+    Embedded systems often use processors that are not the regular x86
+    processors everyone is used to having in his PC. They can be PowerPC
     processors, MIPS processors, ARM processors, etc.</p>
 
-    <p>A compilation toolchain is the set of tools that allows you to 
-    compile code for your system. It consists of a compiler (in our case, 
-    <code>gcc</code>), binary utils like assembler and linker (in our case, 
-    <code>binutils</code>) and a C standard library (for example 
-    <a href="http://www.gnu.org/software/libc/libc.html">GNU Libc</a>, 
-    <a href="http://www.uclibc.org/">uClibc</a> or 
+    <p>A compilation toolchain is the set of tools that allows you to
+    compile code for your system. It consists of a compiler (in our case,
+    <code>gcc</code>), binary utils like assembler and linker (in our case,
+    <code>binutils</code>) and a C standard library (for example
+    <a href="http://www.gnu.org/software/libc/libc.html">GNU Libc</a>,
+    <a href="http://www.uclibc.org/">uClibc</a> or
     <a href="http://www.fefe.de/dietlibc/">dietlibc</a>). The system installed
     on your development station certainly already has a compilation
     toolchain that you can use to compile an application that runs on your
-- 
1.7.9.4

  reply	other threads:[~2012-03-18  8:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18  8:53 [Buildroot] [PATCH 0/5] Docs: Misc. updates and trivial fixes Samuel MARTIN
2012-03-18  8:53 ` Samuel MARTIN [this message]
2012-03-18 21:03   ` [Buildroot] [PATCH 1/5] docs/buildroot.html: cleanup trailing whitespaces Peter Korsgaard
2012-03-18  8:54 ` [Buildroot] [PATCH 2/5] docs/buildroot.html: add new manual location and warning about this page Samuel MARTIN
2012-03-18 21:05   ` Peter Korsgaard
2012-03-18  8:54 ` [Buildroot] [PATCH 3/5] docs: fix busybox url Samuel MARTIN
2012-03-18 21:06   ` Peter Korsgaard
2012-03-18  8:54 ` [Buildroot] [PATCH 4/5] manual: fix typo Samuel MARTIN
2012-03-18 21:08   ` Peter Korsgaard
2012-03-18  8:54 ` [Buildroot] [PATCH 5/5] manual: update Config.in dependency explainations Samuel MARTIN
2012-03-18 16:49   ` Arnout Vandecappelle
2012-03-18 21:13   ` Peter Korsgaard
2012-03-18 16:25 ` [Buildroot] [PATCH 0/5] Docs: Misc. updates and trivial fixes Arnout Vandecappelle

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=1332060843-2786-2-git-send-email-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