From: "Matt Armstrong" <matt+dated+1010273174.cccad3@lickey.com>
Subject: Re: Time to update the copyrights?
Date: Mon, 31 Dec 2001 16:26:07 -0700 [thread overview]
Message-ID: <871yhbx980.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <yl8zbjvv06.fsf@windlord.stanford.edu> (Russ Allbery's message of "Mon, 31 Dec 2001 15:18:33 -0800")
Russ Allbery <rra@stanford.edu> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Should I just add a ", 2002" to all the Gnus files, or should we do
>> that individually to each file as we edit them during the year?
>
> The GNU coding guidelines say to only update them when you make a
> change.
Whats more, there is copyright.el already there to do it for you (at
least in FSF Emacs).
--
matt
next prev parent reply other threads:[~2001-12-31 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 23:12 Lars Magne Ingebrigtsen
2001-12-31 23:18 ` Russ Allbery
2001-12-31 23:26 ` Matt Armstrong [this message]
2002-01-01 0:07 ` Lars Magne Ingebrigtsen
2001-12-31 23:26 ` Lars Magne Ingebrigtsen
2002-01-02 14:49 ` Randal L. Schwartz
2002-01-02 15:00 ` Lars Magne Ingebrigtsen
2002-01-02 16:09 ` Russ Allbery
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=871yhbx980.fsf@squeaker.lickey.com \
--to=matt+dated+1010273174.cccad3@lickey.com \
/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).