|  | 1 | = Viewing Revision Logs = | 
                          |  | 2 | [[TracGuideToc]] | 
                          |  | 3 |  | 
                          |  | 4 | When you browse the repository, it's always possible to query the | 
                          |  | 5 | ''Revision Log'' view corresponding to the path you're currently seeing. | 
                          |  | 6 | This will display a list of the most recent changesets in which the | 
                          |  | 7 | current path or any other path below it has been modified. | 
                          |  | 8 |  | 
                          |  | 9 | == The Revision Log Form == | 
                          |  | 10 |  | 
                          |  | 11 | It's possible to set the revision at which the revision log should | 
                          |  | 12 | start, using the ''View log starting at'' field. An empty value | 
                          |  | 13 | or a value of ''head'' is taken to be the newest changeset. | 
                          |  | 14 |  | 
                          |  | 15 | It's also possible to specify the revision at which the log should | 
                          |  | 16 | stop, using the ''back to'' field. By default, it's left empty, | 
                          |  | 17 | which means the revision log will stop as soon as 100 revisions have | 
                          |  | 18 | been listed. | 
                          |  | 19 |  | 
                          |  | 20 | Also, there are three modes of operation of the revision log. | 
                          |  | 21 |  | 
                          |  | 22 | By default, the revision log ''stops on copy'', which means that | 
                          |  | 23 | whenever an ''Add'', ''Copy'' or ''Rename'' operation is detected, | 
                          |  | 24 | no older revision will be shown. That's very convenient when working | 
                          |  | 25 | with branches, as one only sees the history corresponding to what | 
                          |  | 26 | has been done on the branch. | 
                          |  | 27 |  | 
                          |  | 28 | It's also possible to indicate that one wants to see what happened | 
                          |  | 29 | before a ''Copy'' or ''Rename'' change, by selecting the | 
                          |  | 30 | ''Follow copies'' mode. This will cross all copies or renames changes. | 
                          |  | 31 | Each time the name of the path changes, there will be an additional | 
                          |  | 32 | indentation level. That way, the changes on the different paths | 
                          |  | 33 | are easily grouped together visually. | 
                          |  | 34 |  | 
                          |  | 35 | It's even possible to go past an ''Add'' change, in order to see | 
                          |  | 36 | if there has been a ''Delete'' change on that path, before | 
                          |  | 37 | that ''Add''. This mode corresponds to the mode called | 
                          |  | 38 | ''Show only adds, moves and deletes''. | 
                          |  | 39 | While quite useful at times, be aware that this operation is quite | 
                          |  | 40 | resource intensive. | 
                          |  | 41 |  | 
                          |  | 42 | Finally, there's also a checkbox ''Show full log messages'', | 
                          |  | 43 | which controls whether the full content of the commit log message | 
                          |  | 44 | should be displayed for each change, or only a shortened version of it. | 
                          |  | 45 |  | 
                          |  | 46 | == The Revision Log Information == | 
                          |  | 47 |  | 
                          |  | 48 | For each revision log entry, there are 7 columns shown: | 
                          |  | 49 | 1. The first column contains a pair of radio buttons and should used | 
                          |  | 50 | for selecting the ''old'' and the ''new'' revisions that will be | 
                          |  | 51 | used for [wiki:TracRevisionLog#viewingtheactualchanges viewing the actual changes]. | 
                          |  | 52 | 2. A color code (similar to the one used for the [wiki:TracChangeset#ChangesetHeader changesets]) | 
                          |  | 53 | indicating kind of change. | 
                          |  | 54 | Clicking on this column refreshes the revision log so that it restarts | 
                          |  | 55 | with this change. | 
                          |  | 56 | 3. The '''Date''' at which the change was made. | 
                          |  | 57 | 4. The '''Revision''' number, displayed as `@xyz`. | 
                          |  | 58 | This is a link to the TracBrowser, using that revision as the base line. | 
                          |  | 59 | 5. The '''Changeset''' number, displayed as `[xyz]`. | 
                          |  | 60 | This is a link to the TracChangeset view. | 
                          |  | 61 | 6. The '''Author''' of the change. | 
                          |  | 62 | 7. The '''Log Message''', which contains either a summary or the full commit | 
                          |  | 63 | log message, depending on the value of the ''Show full log messages'' | 
                          |  | 64 | checkbox in the form above. | 
                          |  | 65 |  | 
                          |  | 66 |  | 
                          |  | 67 | == Inspecting Changes Between Revisions == | 
                          |  | 68 |  | 
                          |  | 69 | The ''View changes...'' buttons (placed above and below the list | 
                          |  | 70 | of changes, on the left side) will show the set of differences | 
                          |  | 71 | corresponding to the aggregated changes starting from the ''old'' | 
                          |  | 72 | revision (first radio-button) to the ''new'' revision (second | 
                          |  | 73 | radio-button), in the TracChangeset view. | 
                          |  | 74 |  | 
                          |  | 75 | Note that the ''old'' revision doesn't need to be actually | 
                          |  | 76 | ''older'' than the ''new'' revision: it simply gives a base | 
                          |  | 77 | for the diff. It's therefore entirely possible to easily | 
                          |  | 78 | generate a ''reverse diff'', for reverting what has been done | 
                          |  | 79 | in the given range of revisions. | 
                          |  | 80 |  | 
                          |  | 81 | Finally, if the two revisions are identical, the corresponding | 
                          |  | 82 | changeset will be shown (same effect as clicking on column 5). | 
                          |  | 83 |  | 
                          |  | 84 | == Alternative Formats == | 
                          |  | 85 |  | 
                          |  | 86 | === The !ChangeLog Text === | 
                          |  | 87 |  | 
                          |  | 88 | At the bottom of the page, there's a ''!ChangeLog'' link | 
                          |  | 89 | that will show the range of revisions as currently shown, | 
                          |  | 90 | but as a simple text, matching the usual conventions for | 
                          |  | 91 | !ChangeLog files. | 
                          |  | 92 |  | 
                          |  | 93 | === RSS Support === | 
                          |  | 94 |  | 
                          |  | 95 | The revision log also provides a RSS feed to monitor the changes. | 
                          |  | 96 | To subscribe to a RSS feed for a file or directory, open its | 
                          |  | 97 | revision log in the browser and click the orange 'XML' icon at the bottom | 
                          |  | 98 | of the page. For more information on RSS support in Trac, see TracRss. | 
                          |  | 99 |  | 
                          |  | 100 | ---- | 
                          |  | 101 | See also: TracBrowser, TracChangeset, TracGuide |