From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: 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: Fri, 06 Jan 2012 08:05:39 +0900 [thread overview]
Message-ID: <b4mzke1zr5o.fsf_-_@jpl.org> (raw)
In-Reply-To: <m3fwfufjjl.fsf@stories.gnus.org>
+Cc: emacs-devel@gnu.org
Lars Magne Ingebrigtsen wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Add 2012 to FSF copyright years for Emacs files.
Cf.
http://article.gmane.org/gmane.emacs.diffs/112565
http://article.gmane.org/gmane.emacs.gnus.cvs/11711
> Should this be done for files that haven't changed?
As for emacs-w3m and others I update the copyright years on a file
only when having changed it for the first time in the year. But
Emacs people seem to have been updating it at the beginning of
every year regardless of having been changed or not. And as for
those changes I worked as an engineer to merge changes made in
Emacs and Gnus mutually (I've also updated some extra files, e.g.
gnus-xmas.el and friends, though).
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?
next prev parent reply other threads:[~2012-01-05 23:05 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 ` Katsumi Yamaoka [this message]
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
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=b4mzke1zr5o.fsf_-_@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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.
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).