From: Simon Josefsson <jas@extundo.com>
Subject: Update copyright/license on new files?
Date: Mon, 05 Jan 2004 02:16:20 +0100 [thread overview]
Message-ID: <ilu1xqf42l7.fsf@latte.josefsson.org> (raw)
Some files, e.g. md4.el look like this:
;; Copyright (C) 2001 Taro Kawagishi
;; Author: Taro Kawagishi <tarok@transpulse.org>
;; Keywords: MD4
;; Version: 1.00
;; Created: February 2001
;; This file is part of FLIM (Faithful Library about Internet Message).
;; This program is free software; you can redistribute it and/or modify
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 2, or (at your option)
;; any later version.
;;
;; This program is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
;; GNU General Public License for more details.
;;
;; You should have received a copy of the GNU General Public License
;; along with this program; see the file COPYING. If not, write to the
;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
;; Boston, MA 02111-1307, USA.
Should we change this into the standard Emacs stuff? I assume so, but
thought I'd better check here first.
I believe copyright papers have been assigned for all the stuff I
added, but given the number of files I would appreciate if some
verified this independently.
The author of sasl-scram.el have assigned copyrights to the FSF for a
number of changes, but it is unclear if they apply to sasl-scram.el
too, I've asked assign@gnu.org to clarify. Meanwhile, I haven't
installed that file. It is not critical, so it shouldn't matter (the
SCRAM-MD5 SASL mechanism was never fully adopted, I believe).
next reply other threads:[~2004-01-05 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 1:16 Simon Josefsson [this message]
2004-01-05 1:23 ` Lars Magne Ingebrigtsen
2004-01-05 1:33 ` 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=ilu1xqf42l7.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).