From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: Copyright lines not being updated!
Date: Mon, 4 May 2009 18:10:48 +0200 [thread overview]
Message-ID: <20090504161048.GA16967@thorin> (raw)
Hi all,
Please remember to update copyright lines in files when you commit
copyright significant changes. As a general rule of thumb, if your
commit modifies/adds more than 10 lines of code it's likely going to
be copyright-significant. And if in doubt, it's better to err on the
safe side and update it anyway.
It becomes a PITA at the end of each year when the full list of modified
files needs to be checked manually.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next reply other threads:[~2009-05-04 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 16:10 Robert Millan [this message]
2009-05-04 17:40 ` Copyright lines not being updated! Bean
2009-05-04 17:52 ` Vladimir 'phcoder' Serbinenko
2009-05-04 17:59 ` Vladimir 'phcoder' Serbinenko
2009-05-04 18:00 ` Robert Millan
2009-05-04 19:00 ` Bean
2009-05-04 19:15 ` Bean
2009-05-04 19:44 ` Bean
2009-05-04 20:31 ` Robert Millan
2009-06-03 16:07 ` Felix Zielcke
2009-05-04 17:58 ` Robert Millan
2009-05-04 17:58 ` Felix Zielcke
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=20090504161048.GA16967@thorin \
--to=rmh@aybabtu.com \
--cc=grub-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.