Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Improving the spam.el documentation.
Date: 28 May 2004 12:27:03 -0400	[thread overview]
Message-ID: <4nfz9kecvc.fsf@lifelogs.com> (raw)
In-Reply-To: <87smdk8yxs.fsf@enki.rimspace.net> (Daniel Pittman's message of "Fri, 28 May 2004 23:26:55 +1000")

On Fri, 28 May 2004, daniel@rimspace.net wrote:

> So, in the hope that others don't have to suffer through the same stuff
> that I did I have embarked on updating the spam.el documentation in the
> Gnus manual.
> 
> Assuming, of course, that you are happy to have me rewriting the content
> for you, and that you wouldn't mind doing a technical review of it once
> I am done - I still don't understand it as well as you do. :)

No problem.  I hope you don't have to rewrite too much.  Note that
there's some new features, e.g. CRM114 and spam-report-resend, which
are not in the manual at all (I generally add things after they've
been beta-tested).  I would look at the ChangeLog to see what has been
added to spam.el since the last manual update.

> Also, what is your preferred method for submission of the changes? I can
> send a patch generated against CVS, or whatever else you would like.

Patch is fine.

> I can't commit to Gnus CVS, though, so I can't put it in that way.

I think CVS access can be arranged, but I don't have the authority to
grant it.  Maybe Lars could do it?

Ted



  parent reply	other threads:[~2004-05-28 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 13:26 Daniel Pittman
2004-05-28 15:00 ` Jesper Harder
2004-05-28 16:27 ` Ted Zlatanov [this message]
2004-05-31 13:34   ` Daniel Pittman
2004-06-07 16:56     ` Ted Zlatanov
2004-06-08  1:29       ` Daniel Pittman
2004-06-08 14:31         ` Ted Zlatanov
2004-06-07 17:06     ` Ted Zlatanov
2004-06-08  1:38       ` Daniel Pittman
2004-06-08  2:25         ` Jesper Harder
2004-06-08  3:28           ` Daniel Pittman

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=4nfz9kecvc.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@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).