Edgewall Software

Changes between Version 309 and Version 310 of 0.12/TracFaq


Ignore:
Timestamp:
Jan 21, 2010, 12:16:53 AM (14 years ago)
Author:
Ryan Ollos <ryano@…>
Comment:

Adding info about hook to automatically resync a revision in Trac with the repository

Legend:

Unmodified
Added
Removed
Modified
  • 0.12/TracFaq

    v309 v310  
    663663== Revision Log ==
    664664
    665 === How can I make the TracRevisionLog display the same information as the version control system after a repository revision property edit? === #how-to-update-tracrevlog-after-revprop-edit
    666 
    667 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.
     665=== 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
     666
     667The 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.
     668
     669One 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.
     670
     671{{{
     672TRACENV=<PathToYourTracEnv>
     673trac-admin $TRACENV resync $REV
     674}}}
    668675
    669676----