From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Updating copyright years
Date: Wed, 11 Jan 2012 08:43:19 -0500 [thread overview]
Message-ID: <87lipe9wy0.fsf@lifelogs.com> (raw)
In-Reply-To: <86lipfp1vd.fsf@red.stonehenge.com>
On Tue, 10 Jan 2012 15:35:34 -0800 merlyn@stonehenge.com (Randal L. Schwartz) wrote:
>>>>>> "GM" == Glenn Morris <rgm@gnu.org> writes:
GM> Katsumi Yamaoka wrote:
>>> Emacs people seem to have been updating it at the beginning of
>>> every year regardless of having been changed or not.
GM> Emacs has done it this way for several years, as documented in
GM> admin/notes and as recommended in "Information for Maintainers of GNU
GM> Software":
RLS> That doesn't make it right, and I've gone on the record in the past
RLS> arguing against it.
Doesn't the act of modifying the file to insert the new year make the
file modified and thus require the new year? Heh heh.
(No opinion one way or the other, just found that amusing.)
Ted
next prev parent reply other threads:[~2012-01-11 13:43 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 [this message]
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=87lipe9wy0.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).