From: Erik Selberg <selberg@cs.washington.edu>
Subject: ...slow... saving with default gcc archiving...
Date: 03 Jun 1996 19:07:29 -0700 [thread overview]
Message-ID: <rj7ohn0xqxq.fsf@meitner.cs.washington.edu> (raw)
I did some checking into this... I'm using the "default" Gcc'ing,
which means when I send a mail message, a copy is saved into the file
misc-mail which looks like mbox format. Anyway, this file gets _big_
quickly, and consequentially everytime I save a file, I end up
opening, appending, and saving this 10M file. Takes a couple seconds.
Is there some way of improving this? Either by having misc-mail be
nnml instead of the one file? Or by breaking misc-mail automatically?
Thanks,
-Erik
--
Erik Selberg
"I get by with a little help selberg@cs.washington.edu
from my friends." http://www.cs.washington.edu/homes/selberg
next reply other threads:[~1996-06-04 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-04 2:07 Erik Selberg [this message]
1996-06-20 8:35 ` 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=rj7ohn0xqxq.fsf@meitner.cs.washington.edu \
--to=selberg@cs.washington.edu \
/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).