From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: No "From so-and-so" in ChangeLog
Date: Tue, 21 Mar 2006 11:57:05 +1100 [thread overview]
Message-ID: <87slpcy5r2.fsf@rimspace.net> (raw)
In-Reply-To: <4nfylchqb3.fsf@asimov.bwh.harvard.edu> (Ted Z. Zlatanov's message of "20 Mar 2006 14:25:04 -0500")
"Ted Zlatanov" <tzz@lifelogs.com> writes:
> On 28 Feb 2006, reinersteib+gmane@imap.cc wrote:
>>> 2004-05-27 Teodor Zlatanov <tzz@lifelogs.com>
[...]
> I think Daniel should be the primary for only this change:
>
>>> (spam-report-resend-register-routine): allow spam-report-resend-to
>>> to be a group parameter or a global value (tiny change). From
>>> Daniel Pittman <daniel@rimspace.net>.
>
> And I'll make that fix tomorrow. Daniel, please let me know if that's
> not OK.
No, that is correct - my change really was tiny, and to that specific
bit of code. :)
Daniel
--
Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707 email: contact@digital-infrastructure.com.au
next prev parent reply other threads:[~2006-03-21 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 19:12 Reiner Steib
2006-03-03 9:28 ` Simon Josefsson
2006-03-20 19:25 ` Ted Zlatanov
2006-03-20 21:38 ` Ted Zlatanov
2006-03-21 0:57 ` Daniel Pittman [this message]
2006-03-21 15:28 ` 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=87slpcy5r2.fsf@rimspace.net \
--to=daniel@rimspace.net \
/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).