From: dan <dandenson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] open is so overused these days
Date: Thu, 27 Oct 2022 11:39:05 -0600 [thread overview]
Message-ID: <CAA_JP8Xy58fnXZTWjKd=iQ_g0ytck1HEM9ffaOkD-CFGx=5skw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw676=mrZzPcCb+b6HkO2r9O0-2iO_aDe_zguGGpnAeW5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
'open' has be redefined so it's no longer related to 'free'.
'libre' doesn't roll off the tongue as well but it is basically the answer
to the abuse of the term 'open' so I accept it.
On Thu, Oct 27, 2022 at 9:00 AM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> I do prefer libre as far more aligned to the culture of sharing than
> open has become. libreoffice, libre this, libre that...
>
>
> https://myriadrf.org/news/librecellular-update-5-basic-service/
> https://librerouter.org/
>
>
>
>
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 1762 bytes --]
prev parent reply other threads:[~2022-10-27 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 15:00 Dave Taht
2022-10-27 17:39 ` dan [this message]
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://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA_JP8Xy58fnXZTWjKd=iQ_g0ytck1HEM9ffaOkD-CFGx=5skw@mail.gmail.com' \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.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