From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Evil things with .overview
Date: 09 Aug 1998 11:00:30 +0200 [thread overview]
Message-ID: <m3btpu5y35.fsf@sparky.gnus.org> (raw)
In-Reply-To: "Darren/Torin/Who Ever..."'s message of "08 Aug 1998 05:18:58 -0700"
"Darren/Torin/Who Ever..." <torin@daft.com> writes:
> I want to clear out my admin/sent folder but in a less painful fashion.
> Then it occurred to me that the Summary buffer simply consists of what's
> in the .overview file. That's why the To: can't show up. Well, it's
> generated locally, so I could put the To: line in there instead.
>
> So, if the .overview files doesn't correspond to From: lines to the
> messages, will the Summary buffer just have the wrong info or will I
> blow Gnus bovine mind?
There probably won't be any negative effects if you do this.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-08-09 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-08 12:18 Darren/Torin/Who Ever...
1998-08-09 9:00 ` 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=m3btpu5y35.fsf@sparky.gnus.org \
--to=larsi@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).