From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Copyright lines not being updated!
Date: Wed, 03 Jun 2009 18:07:20 +0200 [thread overview]
Message-ID: <1244045240.3407.9.camel@fz.local> (raw)
In-Reply-To: <20090504203150.GB6649@thorin>
Am Montag, den 04.05.2009, 22:31 +0200 schrieb Robert Millan:
> On Tue, May 05, 2009 at 03:44:27AM +0800, Bean wrote:
> > Hi,
> >
> > git users can add this at the beginning of .git/hooks/pre-commit to
> > run the copyright update test before committing:
> >
> > L1=`git diff --cached --stat 2>/dev/null | gawk '{ if (($2 == "|") &&
> > ($3 > 5)) print $1}'`
> > L2=`grep -lie "Copyright (C).*\(199[0-9]\|200[^9]\) *Free" $L1 2>/dev/null`
> >
> > if test ! -z $L2 ; then
> > echo You should update copyright information for the following files:
> > git diff --cached --stat $L2 2>/dev/null
> > exit 1
> > fi
>
> Note that copyright lines don't _always_ have to be updated. It's
> detrimental to do it when there's no need (bogus copyright assertions
> weaken the legitimate ones).
Well actually the FSF recommendes in the GNU maintainer docs [0] to
update it at the beginning of a year for all files and then be done with
it
By the way I just noticed that emacs has a feaure to update it
automatically on save.
With the GTK version it's at Options -> Customize Emacs -> Top-level
customization group
and then Files -> Before Save Hook -> copyright-update
[0] http://www.gnu.org/prep/maintain/maintain.html#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 of 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."
--
Felix Zielcke
next prev parent reply other threads:[~2009-06-03 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 16:10 Copyright lines not being updated! Robert Millan
2009-05-04 17:40 ` 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 [this message]
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=1244045240.3407.9.camel@fz.local \
--to=fzielcke@z-51.de \
--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.