In the case of SVN version control, a log is written in each version that describes what the new version is updated to do. However, the SVN version of the installed controller is the default once the commit is not allowed to modify the log . But when you commit a version update, some of the features are really forgotten in the diary, The log log for the commit needs to be modified. If you need to get Modify permissions, you must set up a pre-revprop-change hook . The default hook template uses the scripting language under Linux and cannot be run under Windows. So we have to rewrite it, here's how to write a hook script with a batch file. The simplest way to allow Pre-revprop-change.bat to modify the log is to simply empty the contents of the Pre-revprop-change.bat, since the hook script returns 0 to allow modification of any property, as per Subversion's convention.
Log message Modification failed resolution
1. Locate the local storage location of the code warehouse. Open VisualSVN Server Manager, then right-click on the VISUALSVN Server (Local) in the left-hand workspace and select "Properties" in the drop-down list that appears as follows:
Select "Storage" in the pop-up box above to display the following:
2. After finding the above location (copy the address in the run, go directly to the address), click to modify the "log message" of the project name folder, I test the creation of the "Svn-test" project, so to open the folder is the "Svn-test" folder, and then open the folder under the "Hooks" folder, copy "Pre-revprop-change.tmpl" under the above folder and re-command "Pre-revprop-change.bat":
3. Open the Copy and rename the Pre-revprop-change.bat file, add a line "exit 0" at the end of the content and save it. The operation is displayed as follows:
4 the modification was successful. Change the log message again, you can modify the success. (The steps to view the log believe that everyone will, will not repeat it)
PS: The specific modification method reference http://blog.csdn.net/zzfenglin/article/details/51031181, follow this step to find that the last modification is unsuccessful, a little bit of modification here. I hope I can help people who have the same problems as me. .
Resolves an issue where the SVN client failed to modify log message