From: Jack Twilley <jmt+usenet@twilley.org>
Subject: Sending mail now takes way too long
Date: Mon, 28 Jan 2002 10:06:21 -0800 [thread overview]
Message-ID: <86k7u2z6xu.fsf@duchess.twilley.org> (raw)
This is from CVS as of this week.
I C-c C-c to send a message, and it takes 95 seconds to go from
"Sending via mail..." to filing my Gcc, which now takes 10 seconds.
What the heck happened?
Jack.
--
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
next reply other threads:[~2002-01-28 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 18:06 Jack Twilley [this message]
2002-01-29 1:33 ` ShengHuo ZHU
2002-01-29 16:42 ` Jack Twilley
2002-01-29 17:50 ` ShengHuo ZHU
2002-01-29 18:27 ` Jack Twilley
2002-01-30 17:22 ` ShengHuo ZHU
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=86k7u2z6xu.fsf@duchess.twilley.org \
--to=jmt+usenet@twilley.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).