Merge lp:~henninge/launchpad/devel-update-copyright into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Curtis Hovey on 2010-09-27 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 11645 |
| Proposed branch: | lp:~henninge/launchpad/devel-update-copyright |
| Merge into: | lp:launchpad |
| Diff against target: |
203 lines (+135/-41) 3 files modified
buildout-templates/bin/lint.sh.in (+3/-41) utilities/find-changed-files.sh (+45/-0) utilities/update-copyright (+87/-0) |
| To merge this branch: | bzr merge lp:~henninge/launchpad/devel-update-copyright |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Curtis Hovey (community) | code | 2010-09-27 | Approve on 2010-09-27 |
|
Review via email:
|
|||
Commit Message
New utility scripts: find-changed-
Description of the Change
Adds a little script that updates the year information in the copyright header of all changed files. This should make it easy to keep them up to date.
I extracted the code that finds changed files using bzr from lint.sh, which is used by 'make lint'.
No test, this is just a little helper script. Use "bzr diff" after a run to see that it worked.
| Robert Collins (lifeless) wrote : | # |
There is a bzr plugin that can do this without it being in the LP
source tree. It would be nicer to use that.
| Brad Crittenden (bac) wrote : | # |
I'm glad to learn of bzr-update-
Unfortunately when we first put the copyright notice in the files we started with 2009. Using the bzr plugin will change that to use the actual years the file was touched. IANACL so I don't know which is correct but I'd like that to be a decision we make rather than whatever the tool currently writes, so I'd discourage use of the bzr plugin until we can agree.
Note the two tools do not coexist well now as Henning's uses collapsed year ranges, which we prefer, (e.g. "2009-2010") while the plugin produces a comma-separated list. Once the latter is put in the code then this tool is broken.
Perhaps the best effort would be towards improving the plugin.
I'd like for us to get one or the other b/c we spend a lot of time fixing silly copyright notices or leaving them wrong.
| Robert Collins (lifeless) wrote : | # |
I'd like to see the bzr plugin improved if its insufficient. Perhaps a
file in the bzr extensions namespace in the tree, with a config file
to say (use -, and start in 2009).

Thank you so much for this.