I have noticed an inconsistency with some source files in our system, some of which contain source-control checkin comments, and some Do not do it. These comments are automatically added to the top of the file when it is checked:
* $ log: //vm1/Projects/Morpheus/Sleep.bdy-arc $ - - Rev 1.14 Apr 14 2009 15:32:52 John Smith - Fixed bugs 22 9 2 and 2230. This is a lot of work in all companies, with whom I have worked, but I must admit that I struggle to see this point. Generally the comments are not good, it has been left by those people who have long been Have gone, and even when they are of high standards, it is difficult to bind them into physical code changes. It also attacks me, that you are physically changing the file that you are checking. Now, it is not such a problem in such files, which will be compiled, but there may be an accident with others, eg. Javascript files
In fact, my query is that what was the inspiration behind the concept behind providing this functionality for the first time? Does anyone really find these comments useful?
In addition, I would be curious to know whether this feature is generally supported within source control systems. I know about PVCs, VSS and Subversion (), although I am surprised that it is also available in some more popular DAVCSs.
Your help, is always appreciated.
You are right - this is not a very useful feature on balance, modification control system! Yes, companies like an audit trail, but this revision is provided by the log command of the control system; Yes, this means that if there is no revision control system then log is available - but in that case, Fixed bug 1234 is probably not very meaningful :-) And, as you order, the changes To tie down specific rows, you still need the help of the modification control system.
You are also right that changing the file, as it is being done, can cause issues - once I saw the issue where an associate carefully cautions that its code has been compiled, Then it was committed, it should be burnt only because those files were not compiled. It turns out that the comment clear / tmp / * Txt was similar, and C compiler was treating a comment-starting character (and as a complaint, / * as it was already inside a comment).
Another issue with logs in the file is that they only understand to do linear work - once you are developing with many branches (the way the distributed source devices like git / monetary / To encourage market) due to the logging in the source file can generate conflicts only in almost all times.
For this reason, modern tools do not implement this functionality - in fact - its keyword replacement does not intentionally allow log history to be included.
Comments
Post a Comment