From: Jorge P. de Morais Neto via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 49029@debbugs.gnu.org, Leo Famulari <leo@famulari.name>,
Marius Bakke <marius@gnu.org>
Subject: bug#49029: ungoogled-chromium failed to disable malware extension The Great Suspender
Date: Thu, 06 Jan 2022 08:34:34 -0300 [thread overview]
Message-ID: <87r19l14j9.fsf@disroot.org> (raw)
In-Reply-To: <878rvwumjk.fsf@gmail.com>
Hello!
Em [2022-01-03 seg 23:55:59-0500], Maxim Cournoyer escreveu:
> With close to 1500 bugs open, we need *your* help :-). If you think
> this issue is worthy of bringing upstream, please see to it!
Do you know of a way of bringing this issue upstream without a GitHub
account? I could not find one.
Kind regards
--
- Many people hate injustice but few check the facts; this causes more
injustice. Ask me about <https://stallmansupport.org>
- I am Brazilian. I hope my English is correct and I welcome feedback.
- Free Software Supporter: https://www.fsf.org/free-software-supporter
- If an email of mine arrives at your spam box, please notify me.
next prev parent reply other threads:[~2022-01-06 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 21:29 bug#49029: ungoogled-chromium failed to disable malware extension The Great Suspender Jorge P. de Morais Neto via Bug reports for GNU Guix
2021-06-15 13:49 ` Leo Famulari
2021-06-15 14:40 ` Leo Prikler
2021-06-15 16:59 ` Jorge P. de Morais Neto via Bug reports for GNU Guix
2021-06-16 16:31 ` Leo Famulari
2021-06-16 16:33 ` Leo Famulari
2021-06-16 21:09 ` Marius Bakke
2021-06-16 22:17 ` Jorge P. de Morais Neto via Bug reports for GNU Guix
2022-01-04 4:55 ` Maxim Cournoyer
2022-01-06 11:34 ` Jorge P. de Morais Neto via Bug reports for GNU Guix [this message]
2022-01-06 13:46 ` Maxim Cournoyer
2022-01-07 0:09 ` Jorge P. de Morais Neto via Bug reports for GNU Guix
2022-01-07 18:09 ` Maxim Cournoyer
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=87r19l14j9.fsf@disroot.org \
--to=bug-guix@gnu.org \
--cc=49029@debbugs.gnu.org \
--cc=jorge+list@disroot.org \
--cc=leo@famulari.name \
--cc=marius@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).