From: Jesper Harder <harder@myrealbox.com>
Subject: FLIM files (was: Changes committed gnus/lisp (6 files))
Date: Mon, 05 Jan 2004 02:00:25 +0100 [thread overview]
Message-ID: <m3d69zw6om.fsf@defun.localdomain> (raw)
In-Reply-To: <E1AdHMq-0006eL-00@quimby.gnus.org>
"Simon Josefsson" <simon@josefsson.org> writes:
> + * sasl.el, sasl-cram.el, sasl-digest.el, hmac-md5.el, hmac-def.el:
> + New files.
>
> +;;; hmac-def.el --- A macro for defining HMAC functions.
> +
> +;; Copyright (C) 1999, 2001 Free Software Foundation, Inc.
> +
> +;; Author: Shuhei KOBAYASHI <shuhei@aqua.ocn.ne.jp>
> +;; Keywords: HMAC, RFC 2104
> +
> +;; This file is part of FLIM (Faithful Library about Internet Message).
Some general question about files from FLIM:
* Should the versions in Gnus be considered a fork? Should changes in
Gnus CVS be passed upstream to the FLIM maintainers (I don't think
we have done that for some of the existing files derived from FLIM).
* If it _is_ a fork, wouldn't it be wise to rename the files to
different names to reduce the risk of clashes?
next parent reply other threads:[~2004-01-05 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AdHMq-0006eL-00@quimby.gnus.org>
2004-01-05 1:00 ` Jesper Harder [this message]
2004-01-05 1:22 ` FLIM files Lars Magne Ingebrigtsen
2004-01-05 1:30 ` Simon Josefsson
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=m3d69zw6om.fsf@defun.localdomain \
--to=harder@myrealbox.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).