| 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. |
| | 10 | It is also possible to specify the revision at which the log should stop, using the ''Back to'' field. By default it is empty, |
| | 11 | which means the revision log will show the [TracIni#revisionlog-default_log_limit-option default log limit], which defaults to the latest 100 revisions. |
| 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. |
| | 15 | By default, the revision log ''stops on copy'', which means that whenever an ''Add'', ''Copy'' or ''Rename'' operation is detected, no older revision will be shown. That's very convenient when working with branches, as one only sees the history for that branch. |
| 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. |
| | 17 | It is also possible to indicate that one wants include what happened before a ''Copy'' or ''Rename'' change, by selecting the |
| | 18 | ''Follow copies'' mode. This will continue to list all revisions across copies and renames. |
| | 19 | Each time the name of the path changes, there will be an additional indentation level. That way, the changes on the different paths are easily grouped together visually. |
| 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. |
| | 21 | It is even possible to go past an ''Add'' change, in order to see if there has been a ''Delete'' change on that path, before |
| | 22 | that ''Add''. This mode is labeled ''Show only adds, moves and deletes''. The operation can be quite resource intensive and therefore take some time to display. |
| 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. |
| | 29 | For each revision log entry, the following columns are displayed: |
| | 30 | 1. The first column contains a pair of radio buttons and should be used |
| | 31 | for selecting the ''old'' and the ''new'' revisions that will be used for [#InspectingChangesBetweenRevisions viewing the actual changes]. |
| | 32 | 1. A color code (similar to the one used for the |
| | 33 | [TracChangeset#ChangesetHeader changesets]) indicates the kind of 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'' |
| | 36 | 1. The '''Revision''' number, displayed as `@xyz`. |
| | 37 | This is a link to the TracBrowser, using the displayed revision as the base line. |
| | 38 | Next to it, you can see a little "wheel" icon [[Image(htdocs:../common/changeset.png)]], which is clickable and leads to the TracChangeset view for that revision. |
| | 39 | 1. The '''Age'''/'''Date''' at which the change was made. |
| | 40 | Depending on your [/prefs/localization session preference], the date is displayed in either //Relative// or //Absolute// format. |
| | 41 | * //Relative// format shows the '''Age''': the time elapsed as the number of hours, days, weeks, months, or years. |
| | 42 | * //Absolute// format shows the '''Date''' of the revision as a datetime. |
| | 43 | 1. The '''Author''' of the change. |
| | 44 | 1. The '''Log Message''', which contains either the truncated or full commit |
| | 45 | log message, depending on the value of the ''Show full log messages'' |
| 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. |
| | 68 | The revision log also provides an RSS feed to monitor the changes. To subscribe to an RSS feed for a file or directory, open its |
| | 69 | revision log in the browser and click the orange 'XML' icon at the bottom of the page. For more information on RSS support in Trac, see TracRss. |
