From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Should archive server add Message-IDs to the cache?
Date: 18 Mar 1997 22:44:08 +0100 [thread overview]
Message-ID: <m2913kswnr.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Kai Grossjohann's message of 18 Mar 1997 19:02:54 +0100
Kai Grossjohann <grossjohann@ls6.informatik.uni-dortmund.de> writes:
> So there seems to be a conflict. Some people use archive groups, like
> you, and would like one behavior. Other people don't use archive
> groups (like me) and would like the other behavior.
I've switched the caching of Message-IDs off on Gcc.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-03-18 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-18 12:07 Hans de Graaff
1997-03-18 12:55 ` Kai Grossjohann
1997-03-18 14:27 ` Sudish Joseph
1997-03-18 16:33 ` David Moore
1997-03-18 16:43 ` Kai Grossjohann
1997-03-18 17:27 ` David Moore
1997-03-18 18:02 ` Kai Grossjohann
1997-03-18 21:19 ` Paul Franklin
1997-03-18 21:44 ` Lars Magne Ingebrigtsen [this message]
1997-03-19 13:16 ` Fredrik Glockner
1997-03-19 19:39 ` 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=m2913kswnr.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@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).