unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Wayne DePrince Jr." <waynedpj@ingiro.xyz>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: info on move to GNU+Hurd and deprecating Linux-libre
Date: Mon, 06 Apr 2020 14:43:47 -0400	[thread overview]
Message-ID: <198ba877bc153d1303868eb1d7442c43b29f6ed0.camel@ingiro.xyz> (raw)
In-Reply-To: <20200406184017.GA4196@jasmine.lan>

On Mon, 2020-04-06 at 14:40 -0400, Leo Famulari wrote:
> On Mon, Apr 06, 2020 at 02:01:36PM -0400, Wayne DePrince Jr. wrote:
> > ahoy all,
> > 
> > 	hope that everyone is as well as can be.
> > 
> > 	i saw the new post on deprecating Linux in Guix in favor of
> > GNU+Hurd and was just wondering if there is some background on the
> > decision?  i had searched in the mailing list and IRC archives but
> > have
> > not found anything.
> 
> Every good joke has an element of truth, and this was an optimistic
> April Fools joke.
> 
> Work on the Hurd is progressing more quickly than it has in the past,
> and of course we like to use GNU software wherever we can.
> 
> I doubt that Linux support will be deprecated or removed for a long
> time, if ever. It's one of the most useful free software programs :)

LOLOL!  wow, consider me an April FOOL!

with some of the recent rumblings about the Linux kernel i thought
maybe i had missed something bigger .. and apparently i did: April 1 :)

Leo, thank you for pointing out my FOOLishness ;)

peace, w

  reply	other threads:[~2020-04-06 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 18:01 info on move to GNU+Hurd and deprecating Linux-libre Wayne DePrince Jr.
2020-04-06 18:40 ` Leo Famulari
2020-04-06 18:43   ` Wayne DePrince Jr. [this message]
2020-04-06 18:47     ` Wayne DePrince Jr.
2020-04-06 18:52       ` Leo Famulari
2020-04-06 21:22         ` aviva

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=198ba877bc153d1303868eb1d7442c43b29f6ed0.camel@ingiro.xyz \
    --to=waynedpj@ingiro.xyz \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).