From: Jason Rumney <jasonr@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Updating copyright years (was Re: [gnus git] branch master updated: n0-17-447-g55c26cf =1= Add 2012 to FSF copyright years for Emacs files.)
Date: Sat, 07 Jan 2012 12:16:12 +0800 [thread overview]
Message-ID: <87ty48jgfn.fsf@gnu.org> (raw)
In-Reply-To: <b4mzke1zr5o.fsf_-_@jpl.org> (Katsumi Yamaoka's message of "Fri, 06 Jan 2012 08:05:39 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> I used to feel Emacs' way strange. Maybe updating the copyright
> years of Walt Disney's works every year is nonsense. But Emacs'
> way is alike to it. What is TRT?
Emacs is a single "work", so a single copyright date is appropriate. It
is much less error prone to do it all in one sweep, as there is no risk
of a developer making a change to a file (which may be in 11 months
time) and forgetting to update the copyright notice.
prev parent reply other threads:[~2012-01-07 4:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1RilkG-0001VX-GA@quimby.gnus.org>
2012-01-05 11:58 ` [gnus git] branch master updated: n0-17-447-g55c26cf =1= Add 2012 to FSF copyright years for Emacs files Lars Magne Ingebrigtsen
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 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 [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=87ty48jgfn.fsf@gnu.org \
--to=jasonr@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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).