Gnus development mailing list
 help / color / mirror / Atom feed
From: Alex Schroeder <alex@gnu.org>
Subject: Re: [PATCH] spam-stat-save and font-locking
Date: Fri, 02 May 2003 06:38:52 +0200	[thread overview]
Message-ID: <87r87iotcz.fsf@gnu.org> (raw)
In-Reply-To: <4nd6j5s2zq.fsf@lockgroove.bwh.harvard.edu>

Ted Zlatanov <tzz@lifelogs.com> writes:

>> Also I know that we have a feature freeze I send that patch now as I
>> regard that behaviour as a bug.
>
> Committed.  This is small enough that you don't need to have papers on
> file with the FSF, I believe.

I faintly remember RMS saying that in such cases, a little indication
in the ChangeLog.  For a recent patch I received I added "(tiny
change)" after the email address of the author, using
emacs/lisp/ChangeLog as a model.  Not sure whether Gnus is supposed
to follow suite.

Alex.
-- 
http://www.emacswiki.org/cgi-bin/alex.pl



  reply	other threads:[~2003-05-02  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 14:55 Karl Pflästerer
2003-04-29 16:05 ` Ted Zlatanov
2003-05-02  4:38   ` Alex Schroeder [this message]
2003-05-02  8:41     ` Reiner Steib
2003-05-02 16:20       ` 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=87r87iotcz.fsf@gnu.org \
    --to=alex@gnu.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).