On Thu, 19 Jan 2006, Martin Tomes wrote:
> Peter N. Lundblad wrote:
> > On Wed, 18 Jan 2006 kfogel@collab.net wrote:
> >
> >> I asked Mary Ann Moran, a lawyer at CollabNet, about updating all
> >> source files for 2006, versus just updating the ones that changed in
> >> 2006. Here's what she said:
> >>
> >> | Unfortunately, I think I have to say you need to update on a file
> >> | by file basis. Since each individual source code file has its own
> >> | copyright, if the work in that particular copyrighted file is not
> >
> > OK. I have started updating the copyright notices in my last commit. It's
> > not a big deal, but we will forget it all the time.
>
> Isn't this what the pre-commit hook is for?
>
Possibly, but it would be annoying just for this minor thing. You update a
header that gets used in many places, build and test. Then commit and find
that you forgot that damn copyright year and have to rebuild again.
If it was for something more important like style or doxygen markup, then
it would be worth it...
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 19 17:19:39 2006