From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Proposed change of nnmail-remove-list-identifiers
Date: Thu, 20 May 2004 03:53:26 +0200 [thread overview]
Message-ID: <m3d64zn9t5.fsf@defun.localdomain> (raw)
In-Reply-To: <m3zn88imo9.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 16 May 2004 14:25:26 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Jonas Steverud <tvrud@bredband.net> writes:
>
>> -(re-search-forward "^Subject: +\\(\\(R[Ee]: +\\)+\\)R[Ee]: +"
>
> Well, couldn't we use `message-subject-re-regexp'?
Lars, none of Jonas' articles are appearing on news.gnus.org. Could
you take a look at why.
(the only odd thing I can see about them are the very long msg-id's).
--
Jesper Harder <http://purl.org/harder/>
next prev parent reply other threads:[~2004-05-20 1:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 17:28 Jonas Steverud
2004-05-16 12:25 ` Lars Magne Ingebrigtsen
2004-05-20 1:53 ` Jesper Harder [this message]
2004-05-20 2:43 ` Lars Magne Ingebrigtsen
2004-05-20 3:09 ` Jesper Harder
2004-05-20 16:50 ` Lars Magne Ingebrigtsen
2004-05-21 0:37 ` Russ Allbery
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=m3d64zn9t5.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).