From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Build Option Request: VAAPI
Date: Fri, 22 Jan 2021 15:26:45 +0100 [thread overview]
Message-ID: <20210122142645.Pb_dmI5i6_JwJtb706O9zGrG4WNlOjnTjgvHut5_if0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22877@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/22877#issuecomment-765436746
Comment:
> Such a pain to debug chromium. Perhaps Void should consider replacing chromium with its own custom build of ungoogled-chromium... Wouldn't that be truer to the FOSS message anyway (considering how much tracking comes with chromium)?
How does this in any way make any sense to you, how would that reduce any work instead of adding more work?
Chromium is FOSS, chromium is the maintained browser, its FOSS there is not more or less FOSS.
Stop spamming us with ungoogled chromium stuff, I've had enough of it, we said no not once but in multiple different threads and you have to accept it.
prev parent reply other threads:[~2021-01-22 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22877@inbox.vuxu.org>
2021-01-20 21:21 ` ericonr
2021-01-20 21:21 ` [ISSUE] [CLOSED] " ericonr
2021-01-20 21:26 ` dm17
2021-01-20 21:31 ` ericonr
2021-01-20 21:39 ` dm17
2021-01-20 23:08 ` Logarithmus
2021-01-20 23:09 ` Logarithmus
2021-01-20 23:18 ` dm17
2021-01-20 23:28 ` Logarithmus
2021-01-22 12:12 ` dm17
2021-01-22 14:25 ` Duncaen
2021-01-22 14:26 ` Duncaen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210122142645.Pb_dmI5i6_JwJtb706O9zGrG4WNlOjnTjgvHut5_if0@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).