From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Message-ID vs email address
Date: Fri, 21 Feb 2003 15:19:33 +0100 [thread overview]
Message-ID: <878yw9u362.fsf@deneb.enyo.de> (raw)
In-Reply-To: <iluwujtsqoi.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 21 Feb 2003 14:34:37 +0100")
Simon Josefsson <jas@extundo.com> writes:
> Florian Weimer <fw@deneb.enyo.de> writes:
>
>> I've committed Reiner Steib's elisp translation of my Message-ID/email
>> discrimination algorithm. I hope this is enough to confirm that this
>> code is part of Gnus and falls under my assignment contract.
>
> Are your assignment problems solved?
The problems I faced are of a different kind. The FSF has papers for
Gnus (and GCC), but just for Gnus and not Emacs.
> Should we include gpg.el?
Is it still necessary? I suppose it has been obsoleted by PGG, hasn't
it?
Anyway, I'm still not the copyright owner.
next prev parent reply other threads:[~2003-02-21 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 13:26 Florian Weimer
2003-02-21 13:34 ` Simon Josefsson
2003-02-21 14:19 ` Florian Weimer [this message]
2003-02-21 15:38 ` Simon Josefsson
2003-02-21 19:48 ` Florian Weimer
2003-02-21 15:43 ` Kai Großjohann
2003-02-21 19:38 ` Florian Weimer
2003-02-21 20:20 ` 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=878yw9u362.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.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).