From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: gnus-message-archive-group not producing a Gcc header
Date: Fri, 17 Dec 2010 17:41:43 +0100 [thread overview]
Message-ID: <m3r5dgcpx4.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87ipytl5cg.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
> It seems quite odd to need to specify an archive server that is never
> used. Why not only check that the archive-method is non-nil when and if
> it is needed?
I'm sorry -- that's just the way it's supposed to work. In the past, at
least, Gnus has been very liable to get very confused if you try to
store messages to backends that "don't exist". I'd be surprised if that
still wasn't the case.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2010-12-17 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 1:43 Dan Christensen
2010-12-06 14:45 ` Lars Magne Ingebrigtsen
2010-12-06 15:21 ` Julien Danjou
2010-12-06 16:32 ` Dan Christensen
2010-12-16 17:46 ` Lars Magne Ingebrigtsen
2010-12-16 22:29 ` Dan Christensen
2010-12-17 0:17 ` Dan Christensen
2010-12-17 9:29 ` Julien Danjou
2010-12-17 16:41 ` Lars Magne Ingebrigtsen [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=m3r5dgcpx4.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).