[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Q: How to ignore minor changes in text files?

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Wed, 23 Dec 2009 10:21:37 -0500

> 2009/12/23 Bob Archer <Bob.Archer_at_amsi.com>
> > 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
> Thanks for both your input.
> Ryan - is there a convenient place to hook in to the client side? I
> would like to catch this prior it to being displayed as a
> modification.
> Bob - you are correct and I agree with you however the generation
> process takes a while (30s - 1minute) and the controlled package
> files are ghastly to diff from a code readability perspective.
>

Hmm... I see. Can you possibly put the results of the genned code onto a shared location so the devs can just pull the latest down rather than needing to take... wait 30 SECONDS?

Anyway, that is what I plan to do with the binaries that we build right now and put into our repo. The repo is just getting too bloated storing these binaries so next year I am going to modify our build to not source control them and put them in a "latest" folder so devs can grab them when needed. Then I get to play with dumpfilter and pull them out of my repository.

BOb
Received on 2009-12-23 16:22:09 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.