bzr-update-copyright

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> 2010/1/9 John Arbash Meinel <john at arbash-meinel.com>:
>> So having thought about this a bit, I realized there is a *really* good
>> use case for this. I went even one step further and the plugin now
>> installs a 'start_commit' hook. Which means that if you have the plugin
>> installed, and set "auto_update_copyright=True" in your configuration,
>> every time you commit I'll scan for modified files, and then check to
>> make sure that their copyright headers are correct.
>>
>> IOW, it will permanently keep your Copyright headers in sync with the
>> data that Bazaar has for the file. (For files which you modify.)
>>
>> This is a neat enough feature that I'm turning bzr-update-copyright into
>> its own project.
>>
>>  lp:bzr-update-copyright
> 
> That's great.  Can you add it to the plugin guide too?
> 
> 

I would be happy to. If I understood how to do so.

I was able to track down:
lp:~ian-clatworthy/%2Bjunk/bzr-plugins-guide/

Upon checking it out, it then has a couple of .py scripts that seem to
be relevant for rebuilding. I'm not 100% sure what files are
autogenerated and what is not. However, both "add-guide-links.py" and
"mkregistry.py" require an external data file "wiki-data-2.txt" and
"wiki-data.txt", neither of which are present in the branch.


John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktLb0MACgkQJdeBCYSNAAMrjQCdEAKu4XN/SIZELkGHoznhobsu
GqUAoIS9VdWPQFtr4NMsy1L5kkXl/ml3
=fP4V
-----END PGP SIGNATURE-----