From: Mark Eichin <eichin@cygnus.com>
Cc: ding@ifi.uio.no (Gnus Development)
Subject: Re: Archive group is not created when it doesn't exist
Date: 01 May 1996 16:09:38 -0400 [thread overview]
Message-ID: <xe1viig9mv1.fsf@maneki-neko.cygnus.com> (raw)
In-Reply-To: bruin@tasking.nl's message of 01 May 1996 08:17:04 +0200
> monthly basis. But when a new (non-existing) archive group is used, this
> group is not created. Problem might be that I use the same backend for the
This may be the same thing I'm having trouble with; if so, try falling
back to 0.78 and see if it starts working. (I create new groups by
adding new patterns to nnmail-split-methods and respooling... which
works in 0.78, fails in 0.79 and 0.80 (0.80 fixed the loading of
nnml.el, but the nnml-active-number still fails to create the group,
like it did in 0.78.) Since there were major deliberate changes in
there, I was hoping they'd just settle down (though I have filed a bug
report anyway, with the details) but if I don't here from a "bug
fixing zombie" soon (or if 0.81 comes out and it's still broken) I'll
take a look at fixing it myself...
prev parent reply other threads:[~1996-05-01 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-01 6:17 Kees de Bruin
1996-05-01 20:09 ` Mark Eichin [this message]
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=xe1viig9mv1.fsf@maneki-neko.cygnus.com \
--to=eichin@cygnus.com \
--cc=ding@ifi.uio.no \
/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).