From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: copyright for merged code
Date: Thu, 12 May 2005 21:33:43 -0400 [thread overview]
Message-ID: <E1DWP3f-0001wE-9e@fencepost.gnu.org> (raw)
In-Reply-To: <E1DWAtA-0008H3-00@surf.glug.org> (message from Thien-Thi Nguyen on Thu, 12 May 2005 12:25:56 +0200)
i'm presently updating the copyright years in lisp/net/ and
have come upon a doubt: certain files have been merged from
outside emacs, w/ copyright notices that show years prior
to their merging (as far as i can tell from looking at the
"cvs log" output for these files). i am inclined to remove
those years completely, but would like confirmation that this
is the correct approach.
Please keep the years that were put in the notices before
the files were installed into Emacs.
prev parent reply other threads:[~2005-05-13 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 10:25 copyright for merged code Thien-Thi Nguyen
2005-05-12 12:14 ` David Kastrup
2005-05-13 1:33 ` Richard Stallman [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
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=E1DWP3f-0001wE-9e@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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).