From: Alan W. I. <ir...@be...> - 2014-02-24 20:35:16
|
As alluded to in the discussion of our planned change to git, I felt there was no essential purpose to embedding keywords in our files that svn commits would change whenever the svn:keywords property was set appropriately for a file. Ideally commits only occur after testing, but the problem with the keywords approach is the file is changed on commit (e.g., to update the commit date string embedded within the file) so that any attempt to redo the test unexpectedly regenerates much of the build. I believe this convenience issue outweighs any small gain due to embedding redundant (e.g., date of commit, author of commit, name of file) keyword information in the file so accordingly as of revision 13019 I did the massive hand-editing work to remove all the $Author, $Date, $Id, and $Revision keywords from all our files (excluding a few epa_build patch files where $Id had to part of the patch but without any commit updates associated with that $Id keyword). As part of that commiit I also deleted the svn:keywords property for all files. Many files were changed by this process (this is the largest commit I have ever done!), but the tests I used (see the commit message) pretty much insure that I did not introduce any issues with this very large (several days work) number of simple editing changes. N.B. Now that the svn:keywords property has been removed for all files, let's keep it that way! So please _immediately_ take the time to review your svn configuration (e.g., in $HOME/.subversion/config for the Linux command-line svn client) to make sure that new files you commit do not have the svn:keywords property automatically added. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |