From: Carsten Mattner <carstenmattner@googlemail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: Updating copyright years
Date: Wed, 11 Jan 2012 17:36:50 +0100 [thread overview]
Message-ID: <CACY+HvoB0qr6Yv1Whp9_xuxu+X1F7HACoP6z36b7zJc_d5qMwA@mail.gmail.com> (raw)
In-Reply-To: <87y5te8b09.fsf@uwakimon.sk.tsukuba.ac.jp>
On Wed, Jan 11, 2012 at 5:22 PM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> The problem with a permission-by-reference is that the user doesn't
> know what her rights are, not that the owner of the copyright can't
> enforce any restrictions that they choose to maintain (if they're
> enforceable at all, of course). With a well-known license such as the
> GPL, it's really not necessary to provide a copy of the license from a
> legal point of view (except in cases where it's an invariant section
> in an FDL document or the like). However, the GPL is also an advocacy
> document, so providing it in every distribution is a GoodThang.
So if I had something like:
// Copyright __YEAR__ The __PROJECT__ Authors. All Rights Reserved.
// Use of this source code is governed by a __LICENSE__
// license that can be found in the LICENSE file.
Is that good enough?
Looking at src/nsterm.m as an example, it also doesn't have a copy of the
GPL but a long reference to it plus some surrounding explanation.
/*
GNU Emacs 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 3 of the License, or
(at your option) any later version.
*/
Isn't this almost the same reference-only licensing header?
next prev parent reply other threads:[~2012-01-11 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1RilkG-0001VX-GA@quimby.gnus.org>
[not found] ` <m3fwfufjjl.fsf@stories.gnus.org>
2012-01-05 23:05 ` Updating copyright years (was Re: [gnus git] branch master updated: n0-17-447-g55c26cf =1= Add 2012 to FSF copyright years for Emacs files.) Katsumi Yamaoka
2012-01-05 23:14 ` Updating copyright years Glenn Morris
2012-01-05 23:54 ` Katsumi Yamaoka
2012-01-07 0:13 ` Richard Stallman
2012-01-10 23:35 ` Randal L. Schwartz
2012-01-11 13:43 ` Ted Zlatanov
2012-01-11 14:21 ` Carsten Mattner
2012-01-11 16:22 ` Stephen J. Turnbull
2012-01-11 16:36 ` Carsten Mattner [this message]
2012-01-12 4:13 ` Richard Stallman
2012-01-12 6:52 ` Stephen J. Turnbull
2012-01-11 19:39 ` Richard Stallman
2012-01-07 1:45 ` Updating copyright years (was Re: [gnus git] branch master updated: n0-17-447-g55c26cf =1= Add 2012 to FSF copyright years for Emacs files.) Stephen J. Turnbull
2012-01-07 4:16 ` Jason Rumney
2005-05-17 21:48 Updating copyright years Kim F. Storm
2005-05-18 13:20 ` Thien-Thi Nguyen
2005-05-18 22:44 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACY+HvoB0qr6Yv1Whp9_xuxu+X1F7HACoP6z36b7zJc_d5qMwA@mail.gmail.com \
--to=carstenmattner@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).