guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

01/01: website: reduced-binary-seed-bootstrap: Fix typos.


From: Jan Nieuwenhuizen
Subject: 01/01: website: reduced-binary-seed-bootstrap: Fix typos.
Date: Tue, 8 Oct 2019 09:54:32 -0400 (EDT)

janneke pushed a commit to branch master
in repository guix-artwork.

commit cb2d17f78361b0ee92499ee4a766c55784e32ae4
Author: Jan Nieuwenhuizen <address@hidden>
Date:   Tue Oct 8 15:50:07 2019 +0200

    website: reduced-binary-seed-bootstrap: Fix typos.
    
    * website/posts/reduced-binary-seed-bootstrap.md: Fix typos.
---
 website/posts/reduced-binary-seed-bootstrap.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/posts/reduced-binary-seed-bootstrap.md 
b/website/posts/reduced-binary-seed-bootstrap.md
index b7bae8f..ec0ef4f 100644
--- a/website/posts/reduced-binary-seed-bootstrap.md
+++ b/website/posts/reduced-binary-seed-bootstrap.md
@@ -128,8 +128,8 @@ 
provider](https://guix.gnu.org/blog/2015/reproducible-builds-a-means-to-an-end/)
 
 For comparison, _traditional_ distros often have an informally
 specified bootstrap story, usually relying on much bigger binary
-seeds.  We those seeds to weigh in at ~550MB (the size of `debootstrap
---arch=i386
+seeds.  We estimate those seeds to weigh in at ~550MB (the size of
+`debootstrap --arch=i386
 --include=build-essential,dpkg-dev,debhelper,gcc,libc6-dev,make,texinfo
 bullseye ./bullseye-chroot http://deb.debian.org/debian`, with
 `bullseye-chroot/var/cache/apt/archives` removed) in the case of
@@ -176,7 +176,7 @@ simplified C subset.
 
[encouraged](https://lists.nongnu.org/archive/html/tinycc-devel/2017-09/msg00040.html)
 to make MesCC a full blown C99 compliant compiler.  That felt as a
 setback but it gave us the perspective of removing TCC from the
-bootstrap lateron.  Using
+bootstrap later on.  Using
 [Nyacc](https://savannah.nongnu.org/projects/nyacc), the amazing
 parser framework with C99 parser by Matt Wette, has even made that a
 feasible perspective.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]