> > | 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 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. > > *puke* > > I am hoping it is self inflicted vomiting, because this makes our > life simpler. *gives a broom to Jeff so he can clean up his mess*
While it makes it simpler, it does mean that there's almost no point in having those headers at all. It's tempting to just make a CVS keyword that expands to the list. That wouldn't work, a CVS keyword is local to each file. I sure wouldn't want CVS to go about updating hundreds of files just because it feels like it. I think the GDB people have such emacs hack for it to update all the files. _______________________________________________ bug-inetutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-inetutils
