Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sources.redhat.com
Subject: Copyright notices
Date: Sat, 11 Feb 2006 11:08:00 -0000	[thread overview]
Message-ID: <uhd76xif1.fsf@gnu.org> (raw)

Since it took me by surprise, I thought that maybe other maintainers
aren't aware of this text from maintain.texi, which says how to update
copyright years in the files' copyright notices:

    To update the list of year numbers, add each year in which you have
    made nontrivial changes to the package.  (Here we assume you're using
    a publicly accessible revision control server, so that every revision
    installed is also immediately and automatically published.)  When you
    add the new year, it is not required to keep track which files have
    seen significant changes in the new year and which have not.  It is
    recommended and simpler to add the new year to all files in the
    package, and be done with it for the rest of the year.

The last sentence is what took me by surprise, when Richard Stallman
asked people who work on Emacs to add 2006 to _all_ the files in the
distribution, regardless of whether they were modified in that year or
not.

Perhaps we should have a script to do the same once a year, and stop
worrying about updating the individual notices when we modify each
file.


             reply	other threads:[~2006-02-11 11:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11 11:08 Eli Zaretskii [this message]
2006-02-11 11:13 ` Robert Dewar
2006-02-11 16:33   ` Eli Zaretskii
2006-02-12  3:15     ` Robert Dewar
2006-02-11 14:36 ` Daniel Jacobowitz
2006-02-11 16:30   ` Eli Zaretskii
2006-02-11 18:27     ` Daniel Jacobowitz
2006-02-11 19:05       ` Eli Zaretskii
2006-02-11 19:07         ` Daniel Jacobowitz
2006-02-11 19:18           ` Eli Zaretskii
2006-02-11 20:31             ` Daniel Jacobowitz
2006-02-11 19:19           ` Bob Rossi
2006-02-11 21:55             ` Eli Zaretskii
2006-02-12  6:09   ` Jim Blandy

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=uhd76xif1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sources.redhat.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