From: Randy Yates <randy.yates@sonyericsson.com>
Subject: Re: gnus-message-archive-group
Date: 18 May 2004 10:38:13 -0400 [thread overview]
Message-ID: <xxp7jv9dcmi.fsf@usrts005.corpusers.net> (raw)
In-Reply-To: <v9isetltu5.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> On Mon, May 17 2004, Randy Yates wrote:
>
> > I've read some past articles on this problem
>
> Which problem?
I turned on message archiving and am getting one
huge (several 10's of megabytes) file that is
requiring up to one or two minutes to parse when
sending messages and posting articles. Is there
a more elegant way to correct this other than
saving off the archive file in a separate location
and forcing gnus to start adding messages to a new
file?
--
Randy Yates
Sony Ericsson Mobile Communications
Research Triangle Park, NC, USA
randy.yates@sonyericsson.com, 919-472-1124
next prev parent reply other threads:[~2004-05-18 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 21:10 gnus-message-archive-group Randy Yates
[not found] ` <v9isetltu5.fsf@marauder.physik.uni-ulm.de>
2004-05-18 14:38 ` Randy Yates [this message]
[not found] <87fz8ndpo0.fsf@desktop.xx.yy>
2004-06-23 1:43 ` gnus-message-archive-group Hugh Lawson
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=xxp7jv9dcmi.fsf@usrts005.corpusers.net \
--to=randy.yates@sonyericsson.com \
/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).