Comments on: Get Subversion revision information into your source code files http://www.blendedtechnologies.com/get-subversion-revision-information-into-your-source-code-files/37 Established January 2005 Tue, 14 Oct 2008 00:08:11 +0000 http://wordpress.org/?v=2.0 by: Administrator http://www.blendedtechnologies.com/get-subversion-revision-information-into-your-source-code-files/37#comment-21 Wed, 21 Sep 2005 14:23:34 +0000 http://www.blendedtechnologies.com/get-subversion-revision-information-into-your-source-code-files/37#comment-21 John, I'm glad you mentioned that. Using the $Rev$ token is good alternative depending on your needs. I prefer my method because it updates every file to the latest revision number. Using the Rev keyword will only update $Rev$ in a file when it is committed. Suppose someone sends me just one file from multi-file app I wrote, and that one file wasn't commited since revision 1. The $Rev: 1$ in the file wouldn't really give me much information. But if every file he had, had the latest revision number, then just from that one file, I could get the whole app from my repository and start debugging. "Interesting tip, but perhaps I’m missing something: How is this different/better/worse than setting the svn:keywords property to “Rev” for the file(s) in question, and let svn automatically expand the $Rev$ token when the file is committed?" John, I’m glad you mentioned that. Using the $Rev$ token is good alternative depending on your needs. I prefer my method because it updates every file to the latest revision number. Using the Rev keyword will only update $Rev$ in a file when it is committed. Suppose someone sends me just one file from multi-file app I wrote, and that one file wasn’t commited since revision 1. The $Rev: 1$ in the file wouldn’t really give me much information. But if every file he had, had the latest revision number, then just from that one file, I could get the whole app from my repository and start debugging.

“Interesting tip, but perhaps I’m missing something: How is this different/better/worse than setting the svn:keywords property to “Rev” for the file(s) in question, and let svn automatically expand the $Rev$ token when the file is committed?”

]]> by: John Burkhard http://www.blendedtechnologies.com/get-subversion-revision-information-into-your-source-code-files/37#comment-19 Wed, 21 Sep 2005 12:59:31 +0000 http://www.blendedtechnologies.com/get-subversion-revision-information-into-your-source-code-files/37#comment-19 Interesting tip, but perhaps I'm missing something: How is this different/better/worse than setting the svn:keywords property to "Rev" for the file(s) in question, and let svn automatically expand the $Rev$ token when the file is committed? Interesting tip, but perhaps I’m missing something: How is this different/better/worse than setting the svn:keywords property to “Rev” for the file(s) in question, and let svn automatically expand the $Rev$ token when the file is committed?

]]>