title: pre-revprop-change hook either failed
body: <p>I don't know if this hook is out-of-box or if mine is just messed up and I just need to replace it but when I go and try to edit a log comment on a commit I get this error message:</p>
  
  <blockquote>
    <p>DAV request failed; it’s possibly that the repository’s pre-revprop-change hook either failed or is non-existent<br>
    At least one property change failed; repository is unchanged<br>
    Error setting property ‘log’</p>
  </blockquote>
  
  <p>I'm using Tortoise v1.6.7 but have had this problem all along since I installed Tortoise, just never looked into it but it's extremely annoying.</p>
  
  <p><a href="http://jacqueschirag.wordpress.com/2007/07/22/changing-revision-property-in-subversion-with-tortoisesvn/" rel="noreferrer">So I found this article</a>.</p>
  
  <p>However since I can't figure out how to do svn command line calls with Tortoise, I simply went into the repository and opened up the pre-refprop-change template and below is what's in it.</p>
  
  <pre><code>REPOS="$1"
  REV="$2"
  USER="$3"
  PROPNAME="$4"
  ACTION="$5"
  
  if [ "$ACTION" = "M" -a "$PROPNAME" = "svn:log" ]; then exit 0; fi
  
  echo "Changing revision properties other than svn:log is prohibited" &gt;&amp;2
  exit 1
  </code></pre>
  
  <p>So still trying to figure out how to change this so that Tortoise (subversion that is) allows me to edit comments.  Why would one desire to edit comments?  Because there are many times I f'd up and forgot to add more comments after a commit after I realized I missed x,y,z that should have been in the comments after the fact.  Happens to anyone.  While it's a security risk to allow developers to do this, we back up our repository every 2 hours so if anyone goes through and deletes them, oh well, I am willing to take that risk as we have this backed up.  That risk should not overshadow the ability to fix comments at will.</p>