Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: C-d heuristics
Date: Wed, 24 Apr 2002 13:25:50 +0200	[thread overview]
Message-ID: <vafit6hpcch.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87ofg9ol2b.fsf@uwo.ca> (Dan Christensen's message of "Tue, 23 Apr 2002 23:02:52 -0400")

Dan Christensen <jdc+news@uwo.ca> writes:

> Could someone please apply this patch?  I have papers on file.

I applied the patch and wrote this ChangeLog entry:

2002-04-24  Kai Großjohann  <Kai.Grossjohann@CS.Uni-Dortmund.DE>
	From Dan Christensen <jdc+news@uwo.ca>.
	
	* nndoc.el (nndoc-type-alist, nndoc-lanl-gov-announce-type-p)
	(nndoc-transform-lanl-gov-announce, nndoc-generate-lanl-gov-head):
	Recognize math postings properly.  Extract Date and email address
	correctly.  Create Date and From header for revised versions.  Get
	rid of spurious \\ lines.  Detect end of message correctly.
	Correctly rephrase the URL.

I think the ChangeLog entry could be improved.  For example, it's not
clear to me what does "correctly" mean.  I think the idea is that in
ChangeLog entries it is said what happens.  So for example, if you
deleted an X from each URL, it should say "Delete X from URL."
instead of "Correctly rephrase URL."

I didn't try to read the code to really grok what's going on; I hope
you aren't angry at me for being so lazy.

Are you willing to provide an improved ChangeLog entry?

kai
-- 
Silence is foo!



  reply	other threads:[~2002-04-24 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12 21:48 Dan Christensen
2002-03-12 22:08 ` Ted Stern
2002-04-24  3:02 ` Dan Christensen
2002-04-24 11:25   ` Kai Großjohann [this message]
2002-04-24 18:59     ` Dan Christensen
2002-04-24 19:36       ` Kai Großjohann
2002-04-24 19:33 Ted Stern
2002-04-25  7:43 ` Kai Großjohann
2002-04-25  7:44 ` Kai Großjohann
2002-04-25 19:11 Ted Stern
2002-04-26 11:10 ` Kai Großjohann

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=vafit6hpcch.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).