From: Simon Josefsson <jas@extundo.com>
Subject: Re: [patch] message-fetch-field, message-remove-header called
Date: Sat, 07 Jun 2003 01:40:18 +0200 [thread overview]
Message-ID: <iluadcuvkpp.fsf@latte.josefsson.org> (raw)
In-Reply-To: <84ptlq3ogb.fsf@lucy.is.informatik.uni-duisburg.de> (Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "Fri, 06 Jun 2003 23:07:00 +0200")
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> Gnah. I wish I had fencepost access so I didn't have to ask for the
> copyright situation every time. Or maybe a less bad memory would be
> sufficient. This time, I'm too ashamed to ask...
EMACS GNUS Benjamin Rutt
Assigns past and future changes to gnus. (message.el)
> I've tried various addresses to reactivate my fencepost account; does
> anyone here know which one works? (I believe system-hackers sent me
> a nice autoreply, but nothing happened.)
Perhaps accounts at gnu.org works?
next prev parent reply other threads:[~2003-06-06 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 18:43 [patch] message-fetch-field, message-remove-header called improperly Benjamin Rutt
2003-06-06 21:07 ` [patch] message-fetch-field, message-remove-header called Kai Großjohann
2003-06-06 23:40 ` Simon Josefsson [this message]
2003-06-07 1:03 ` Benjamin Rutt
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=iluadcuvkpp.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).