parent
4c12433a6a
commit
6f9ec4cc4d
|
@ -1306,8 +1306,8 @@ product. No. They put a paragraph in their documentation,
|
|||
urging people to *delete* links to libreboot.org, and link to them. *They were
|
||||
out for blood*.
|
||||
|
||||
Fork attempt 2: GNU
|
||||
-------------------
|
||||
FSF's 2nd fork attempt
|
||||
---------------------
|
||||
|
||||
So I've responded in kind, ever since. Regardless of whether they succeed or
|
||||
whether they are competent, a thought exists in their head. A dream, you could
|
||||
|
@ -1326,7 +1326,8 @@ fork of coreboot. The name just works.
|
|||
GNU did rename their project, but only after I forced them to do so. I forced
|
||||
them to do so, by exposing the moral bankrupcy on their part, in their initial
|
||||
effort to steal the Libreboot name. Their initial plan was to create a newly
|
||||
established *GNU Libreboot* project.
|
||||
established *GNU Libreboot* project. The name that they *now* use was created
|
||||
by me, and I made them use it.
|
||||
|
||||
By 2023-12-12, GNU's fork had a new RC imminent for release, on this day, and it
|
||||
was still based largely on Libreboot 20220710, with only superficial changes on
|
||||
|
@ -1406,8 +1407,8 @@ and now:
|
|||
Canoeboot
|
||||
---------
|
||||
|
||||
Purely for my own entertainment, I decided to re-create blob-free Libreboot *myself*.
|
||||
It is the same one that GNU uses, that Libreboot previously used, before
|
||||
Purely for my own entertainment, I decided to re-create blob-free
|
||||
Libreboot *myself*, exactly the same one that Libreboot used in the past, before
|
||||
it adopted the modern [Binary Blob Reduction Policy](policy.md) - GNU started
|
||||
their new project, specifically because it opposed the new policy in Libreboot.
|
||||
|
||||
|
|
Loading…
Reference in New Issue