From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: utterly bogus "How many articles from ... (available ..., default ...)"
Date: Sun, 26 Jun 2011 12:21:41 +0200 [thread overview]
Message-ID: <m3iprsx58q.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <878vso28yr.fsf@micropit.couberia.bzh>
pmlists@free.fr (Peter Münster) writes:
> I think, the OP suggests, that the back-end should provide more or better
> information, if possible.
Yes, that would be nice. However, this particular user has reported the
same thing, like, four thousand times now, and there's just so many
times that I feel like repeating the same thing.
Doing something about this is going to happen in the next Gnus
development cycle.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-06-26 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 11:58 jidanni
2011-06-26 9:43 ` Lars Magne Ingebrigtsen
2011-06-26 10:17 ` Peter Münster
2011-06-26 10:21 ` Lars Magne Ingebrigtsen [this message]
2011-06-28 1:09 ` jidanni
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=m3iprsx58q.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).