I had to deal with svn repository internal the last few days. Two questions came up:
a)
Once a while ago we had to add the property svn:eol native to the svn configurarion in order to be able to commit to the repository. Currently this seems not to be required anymore.
Should it be enabled anyway? Or should it attached to new files? (svn add .....)
Some of the source files carry the property, others don't.
b)
Some times ago Sebastion added the svn:keywords property to all source files in order to automatically insert the $Id, $Author and $URL tags.
Again, some files in the repository carry this prop, others don't.
@Alan: I suppose you have the most sound knowledge of the topic. Could you, please, shed some light on this issue? How has svn to be configured locally? And should everyone who comes across a missing keyword prop or a unneeded svn:eol prop delete/add it?
Peter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had to deal with svn repository internal the last few days. Two questions came up:
a)
Once a while ago we had to add the property svn:eol native to the svn configurarion in order to be able to commit to the repository. Currently this seems not to be required anymore.
Should it be enabled anyway? Or should it attached to new files? (svn add .....)
Some of the source files carry the property, others don't.
b)
Some times ago Sebastion added the svn:keywords property to all source files in order to automatically insert the $Id, $Author and $URL tags.
Again, some files in the repository carry this prop, others don't.
@Alan: I suppose you have the most sound knowledge of the topic. Could you, please, shed some light on this issue? How has svn to be configured locally? And should everyone who comes across a missing keyword prop or a unneeded svn:eol prop delete/add it?
Peter