unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Bug tracker spam
@ 2022-01-06 18:56 Tobias Geerinckx-Rice
  2022-01-06 21:37 ` Ricardo Wurmus
  0 siblings, 1 reply; 2+ messages in thread
From: Tobias Geerinckx-Rice @ 2022-01-06 18:56 UTC (permalink / raw)
  To: guix-devel

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

All,

I've asked the debbugs crew over e-mail how to deal with [0], 
assuming there's a way to close bugs without pinging a malicious 
sender.

Please, nobody respond to or modify it in the mean time.

I'll follow up with a question on how we're supposed to moderate 
bugs if the tracker & archive sit *in front of* the moderation 
queue…

It's frankly a miracle that this doesn't happen constantly.

Kind regards,

T G-R

[0]: https://issues.guix.gnu.org/53051

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Bug tracker spam
  2022-01-06 18:56 Bug tracker spam Tobias Geerinckx-Rice
@ 2022-01-06 21:37 ` Ricardo Wurmus
  0 siblings, 0 replies; 2+ messages in thread
From: Ricardo Wurmus @ 2022-01-06 21:37 UTC (permalink / raw)
  To: Tobias Geerinckx-Rice; +Cc: guix-devel


Tobias Geerinckx-Rice <me@tobias.gr> writes:

> I've asked the debbugs crew over e-mail how to deal with [0], assuming
> there's a way to close bugs without pinging a malicious sender.

FYI: I adjusted the way we sync debbugs data (added a “--delete”) so now
that spam bug is also gone from issues.guix.gnu.org.

-- 
Ricardo


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-01-06 21:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-06 18:56 Bug tracker spam Tobias Geerinckx-Rice
2022-01-06 21:37 ` Ricardo Wurmus

Code repositories for project(s) associated with this 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).