From: Alberto Luaces <aluaces@udc.es>
To: ding@gnus.org
Subject: Re: Updating definition of "bogus" groups?
Date: Wed, 22 May 2024 11:27:37 +0200 [thread overview]
Message-ID: <871q5ufb7a.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <87zfsi9408.fsf@ericabrahamsen.net>
> This seems like it would be more handy for cleaning up "dangling"
> groups.
>
> Does anyone have an opinion on that idea, one way or the other?
I would remove the term `bogus` altogether, it's too vague, and replace
it with something more descriptive. This is independent from the fact
that the behaviour could be more useful, as you describe.
--
Alberto
next prev parent reply other threads:[~2024-05-22 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 22:47 Eric Abrahamsen
2024-05-22 9:27 ` Alberto Luaces [this message]
2024-05-22 14:23 ` Emanuel Berg
2024-05-22 17:25 ` Russ Allbery
2024-05-23 0:47 ` Emanuel Berg
2024-05-23 2:30 ` Russ Allbery
2024-05-23 3:54 ` Eric Abrahamsen
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=871q5ufb7a.fsf@eps142.cdf.udc.es \
--to=aluaces@udc.es \
--cc=ding@gnus.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).