> On Dec 23, 2009, at 00:45, Julian Mitchell wrote: > > > The project that I am working on utilises a code generation tool. > The header of every source file includes a comment with a date\time > stamp of when it was generated. The problem is that every time the > code is generated the svn change check algorithm marks all files as > having been changed even though only a handful have actually had > actual code changes. > > > > Is there a way to tailor the change check algorithm with, say, a > regex, to ignore certain contents of a text file e.g. comment > lines? > > To my knowledge, there is not. You could consider writing a client- > side script that committers should run before checking in source, > to normalize such comment lines e.g. to remove the date/time. You > could also write a companion server-side hook script to reject any > commit where the only difference is such a comment line.
I think the current wisdom is, don't source control files that can be generated. So, for the same reason you [usually] don't store binaries that you build from your source don't store code files that are generated. Make the generation part of the build so that any dev running the build script gets the files generated for them. BOb
