CODEWITHSUNDEEP
svnvisualsvnpre-commit
Abel
Abel

Reputation: 57159

Best practices with SVN for files that always "change" with no change

We have a project that references files in a Common-directory. Whenever that project is opened or compiled, these files are copied. Because the timestamp changes, Subversion sees that as changes. I only want to commit new changes of the general Common-directory, or actual changes in the project. Not the auto-copies that the compiler performs for me.

How do I keep the directory and the files in SVN, but prevent these non-changes to be seen as changes? Is there some "best practice" or "preferred" way of dealing with such situations?

Upvotes: 1

Views: 246

Answers (2)

Clutch
Clutch

Reputation: 7600

I would think a simple svn:ignore on the common directory would do. The files that don't really change should be checked in to a separate project. You would have to tell your developers that they will have to checkout the two project but only check in the project with the files that really change.

Upvotes: 2

Travis Gockel
Travis Gockel

Reputation: 27633

Typically, you don't want to put compiler-generated anything into your repository. Use svn:ignore to ignore these things.

Upvotes: 7

Related Questions