From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Virtual groups weirdness
Date: Thu, 12 May 2011 07:58:55 -0500 [thread overview]
Message-ID: <87d3jo5b3k.fsf@lifelogs.com> (raw)
In-Reply-To: <87r5842q9y.fsf@gmail.com>
On Thu, 12 May 2011 11:59:21 +0200 Antoine Levitt <antoine.levitt@gmail.com> wrote:
AL> 11/05/11 23:43, Ted Zlatanov
>> Also I would disallow any group with a nnvirtual backend, not just the
>> one we're generating. There's little point in making virtual groups of
>> virtual groups, so that would also fix the issue you're reporting.
AL> That'd certainly be easier to implement (just match
AL> ^nnvirtual). However, I'm not sure it's the right thing to do. Users
AL> could in principle have a tree of virtual groups. I'm not sure if anyone
AL> actually does that, but it seems arbitrary to forbid it.
If you think about the use cases, virtual groups are rare anyhow.
Meta-virtual groups are probably extremely rare as legitimate use cases.
But this is just my opinion; maybe others are using meta-virtuals happily.
Ted
next prev parent reply other threads:[~2011-05-12 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 9:46 Antoine Levitt
2011-05-11 11:07 ` Antoine Levitt
2011-05-11 21:43 ` Ted Zlatanov
2011-05-12 9:59 ` Antoine Levitt
2011-05-12 12:58 ` Ted Zlatanov [this message]
2011-05-30 19:49 ` Lars Magne Ingebrigtsen
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=87d3jo5b3k.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).