From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: another problem with base64.
Date: 09 Nov 2000 13:28:52 +0100 [thread overview]
Message-ID: <vafd7g5e3cr.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3em0lqra4.fsf@wazabi.tpi.pl>
On 09 Nov 2000, Jakub Martyński wrote:
> Why base64.el is in contrib directory?
Because a copyright assignment to the FSF is lacking, base64.el can't
be distributed with Emacs. All the stuff that can't be distributed
with Emacs is in the contrib directory for easier recognition. This
way, Dave can just copy the lisp directory over to Emacs 21 and Bob's
his uncle.
Fwiw, base64.el isn't needed in Emacs since the relevant functions are
implemented in C since Emacs 20.5 or so.
kai
--
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing
prev parent reply other threads:[~2000-11-09 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 12:11 Jakub Martyński
2000-11-09 12:28 ` Kai Großjohann [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=vafd7g5e3cr.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).