Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: FLIM files
Date: Mon, 05 Jan 2004 02:30:26 +0100	[thread overview]
Message-ID: <iluu13b2nd9.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3d69zw6om.fsf@defun.localdomain> (Jesper Harder's message of "Mon, 05 Jan 2004 02:00:25 +0100")

Jesper Harder <harder@myrealbox.com> writes:

> "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:

Good questions.  I don't really know the answer, here's just my
opinion:

> * 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).

Yes, ideally.  For PGG, I recall CC'ing the PGG authors on some
patches initially, but I'm not sure anyone read them or did anything
with the patches, so I stopped.  Maybe we could submit all
modifications between FLIM and Gnus 5.10?  Perhaps better to ask
first.  Any FLIM people reading this list?

As for the SASL package, when I worked on getting copyright
assignments signed for it, I said the reason was to be able to include
the files in Gnus.  Renaming or forking wasn't discussed then.

> * If it _is_ a fork, wouldn't it be wise to rename the files to
>   different names to reduce the risk of clashes?

I dunno.  The best would be to have Gnus nurse the files into Emacs
proper, and accepting patches from the FLIM team as we proceed, and
possibly also send patches to the FLIM team if they are interested.
I.e., make Emacs the canonical location for the files, and the Gnus
and FLIM teams maintain their own more frequently modified copies.




      parent reply	other threads:[~2004-01-05  1:30 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 ` FLIM files (was: Changes committed gnus/lisp (6 files)) Jesper Harder
2004-01-05  1:22   ` FLIM files Lars Magne Ingebrigtsen
2004-01-05  1:30   ` Simon Josefsson [this message]

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=iluu13b2nd9.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).