Changes between Version 311 and Version 312 of 0.12/TracFaq

Timestamp:

Jan 21, 2010, 11:58:35 PM (14 years ago)

Author:

Ryan Ollos <ryano@…>

Comment:

Clarification on setting up post-revprop-change hook in Subversion

0.12/TracFaq

@@ -663 +663 @@
 === How can I make the TracRevisionLog display the same information as the version control system after an edit to a repository revision property? === #how-to-update-tracrevlog-after-revprop-edit
 
-The solution is the same as discussed [TracFaq#how-do-i-get-trac-to-resync-the-timeline-with-my-subversion-repository here]. The TracRevisionLog must be resynced with the repository after an edit to a revision property in the version control back-end. The `trac-admin resync` command can be used to resync the entire repository or a single revision. See `tracadmin help` or TracAdmin#FullCommandReference for more details.
-
-One can even create a hook to automatically resync the revision history in Trac with that in the repository following a property edit. In Subversion, adding the following to the post-revprop-change hook will enable this behavior.
-
-{{{
-TRACENV=<PathToYourTracEnv>
+The solution is the same as discussed [TracFaq#how-do-i-get-trac-to-resync-the-timeline-with-my-subversion-repository here]. The TracRevisionLog must be resynced with the repository after an edit to a revision property in the version control back-end. The `trac-admin resync` command can be used to resync the entire repository or a single revision. See `trac-admin help` or TracAdmin#FullCommandReference for more details.
+
+One can even create a hook to automatically resync the revision history in Trac with that in the repository following a property edit.
+
+In Subversion, make a copy of the post-revprop-change template, define `TRACENV`, and add the following to the hook script:
+{{{
 trac-admin $TRACENV resync $REV
 }}}