While I think it's a good idea, I'm not sure:
* discovery of the CVS $Id$ tags of every .module, .inc, .theme, .css .xtmpl, etc. storing of these version numbers
this is a good way to implement. Somewhere in the CVS docs, they caution AGAINST using $Id$ as a version number. Off the top of my head, I can think of some reasons why: * CVS server crashes, wiping out all histories. Revisions start over. * Just because I patch my local copy doesn't mean I committed my patch to a server somewhere, or that I changed the $Id$ of my local copy. Comparisions would fail. * $Id$ isn't everywhere, is it? Does it always lock us into CVS forever, or are there easy equivalents in SVN? And, if we did switch to another RCS in the future, what happens to all the $Id$s we've been basing comparisons on? -- Morbus Iff ( you are nothing without your robot car, NOTHING! ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ O'Reilly Author, Weblog, Cook: http://www.oreillynet.com/pub/au/779 icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus