From: TSUCHIYA Masatoshi <tsuchiya@namazu.org>
Subject: Re: [spam.el] Misleading messages on group exit
Date: Thu, 20 May 2004 16:48:47 +0000 [thread overview]
Message-ID: <87pt8znixc.fsf@namazu.org> (raw)
In-Reply-To: <4nlljn41oq.fsf@lifelogs.com> (Ted Zlatanov's message of "20 May 2004 10:23:49 -0400")
>> On 20 May 2004 10:23:49 -0400
>> tzz@lifelogs.com ("Ted Zlatanov") said as follows:
>> I'd like to propose the attached change, which simplifies the
>> condition to display status messages.
> I'm OK with this, it improves my version nicely.
I have installed my prposed change to CVS with your approval.
>I didn't see you in the ChangeLog
That's strange. Could you check lisp/ChangeLog?
By the way, thank you for your kind comments.
--
TSUCHIYA Masatoshi
next prev parent reply other threads:[~2004-05-20 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 12:08 Reiner Steib
2004-05-11 6:37 ` TSUCHIYA Masatoshi
2004-05-12 5:09 ` TSUCHIYA Masatoshi
2004-05-14 19:23 ` Ted Zlatanov
2004-05-16 15:56 ` TSUCHIYA Masatoshi
2004-05-17 14:12 ` Ted Zlatanov
2004-05-20 2:29 ` TSUCHIYA Masatoshi
2004-05-20 14:23 ` Ted Zlatanov
2004-05-20 16:48 ` TSUCHIYA Masatoshi [this message]
2004-05-20 17:42 ` Ted Zlatanov
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=87pt8znixc.fsf@namazu.org \
--to=tsuchiya@namazu.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).