Changes between Version 318 and Version 319 of 0.12/TracFaq
- Timestamp:
- Aug 15, 2010, 6:42:55 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
0.12/TracFaq
v318 v319 539 539 540 540 {{{ 541 trac-admin <yourprojenv> re sync541 trac-admin <yourprojenv> repository resync <reponame> 542 542 }}} 543 543 … … 697 697 === 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 698 698 699 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 re sync` command can be used to resync the entire repository or a single revision. See `trac-admin help` or TracAdmin#FullCommandReference for more details.699 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 repository resync` command can be used to resync the entire repository or a single revision. See `trac-admin help` or TracAdmin#FullCommandReference for more details. 700 700 701 701 One can even create a hook to automatically resync the revision history in Trac with that in the repository following a property edit. … … 703 703 In Subversion, make a copy of the post-revprop-change template, define `TRACENV` and `TRACADMIN`, and add the following to the hook script: 704 704 {{{ 705 $TRACADMIN $TRACENV resync$REV705 $TRACADMIN $TRACENV changeset modified <reponame> $REV 706 706 }}} 707 707