From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Customizing article expiry
Date: Mon, 07 Jan 2002 19:48:53 +0100 [thread overview]
Message-ID: <m3hepyj8tm.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m14rly3t6g.fsf@reader.newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> Ick.. It never dawned on my there were many ChangeLogs. So I guess
> there isn't one general ChangeLog that covers all gnus eh?
No, there's one ChangeLog for each directory. All the action is in
the lisp/ChangeLog file.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2002-01-07 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <u1u153jr.fsf@online.no>
[not found] ` <m1k7uwda8b.fsf@reader.newsguy.com>
[not found] ` <m3u1u08yxy.fsf@quimbies.gnus.org>
[not found] ` <x7n0zrpgzu.fsf@reader.newsguy.com>
[not found] ` <1yh3pf0x.fsf@online.no>
2002-01-07 16:28 ` Harry Putnam
2002-01-07 16:35 ` Paul Jarc
2002-01-07 16:58 ` Christoph Conrad
2002-01-07 18:35 ` Harry Putnam
2002-01-07 18:48 ` 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=m3hepyj8tm.fsf@quimbies.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).