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: |
---|
49 | 1. The first column contains a pair of radio buttons and should be used |
---|
50 | for selecting the ''old'' and the ''new'' revisions that will be |
---|
51 | used for [wiki:TracRevisionLog#viewingtheactualchanges viewing the actual changes]. |
---|
52 | 1. A color code (similar to the one used for the |
---|
53 | [wiki:TracChangeset#ChangesetHeader changesets]) indicating kind of change. |
---|
54 | Clicking on this column refreshes the revision log so that it restarts |
---|
55 | with this change. |
---|
56 | 1. The '''Revision''' number, displayed as `@xyz`. |
---|
57 | This is a link to the TracBrowser, using the displayed revision as the base line. |
---|
58 | 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. |
---|
59 | 1. The '''Date''' at which the change was made. |
---|
60 | The date is displayed as the time elapsed from the date of the revision. The time |
---|
61 | elapsed is displayed as the number of hours, days, weeks, months, or years. |
---|
62 | 1. The '''Author''' of the change. |
---|
63 | 1. The '''Log Message''', which contains either the truncated or full commit |
---|
64 | log message, depending on the value of the ''Show full log messages'' |
---|
65 | checkbox in the form above. |
---|
66 | |
---|
67 | |
---|
68 | == Inspecting Changes Between Revisions == |
---|
69 | |
---|
70 | The ''View changes...'' buttons (placed above and below the list |
---|
71 | of changes, on the left side) will show the set of differences |
---|
72 | corresponding to the aggregated changes starting from the ''old'' |
---|
73 | revision (first radio-button) to the ''new'' revision (second |
---|
74 | radio-button), in the TracChangeset view. |
---|
75 | |
---|
76 | Note that the ''old'' revision doesn't need to be actually |
---|
77 | ''older'' than the ''new'' revision: it simply gives a base |
---|
78 | for the diff. It's therefore entirely possible to easily |
---|
79 | generate a ''reverse diff'', for reverting what has been done |
---|
80 | in the given range of revisions. |
---|
81 | |
---|
82 | Finally, if the two revisions are identical, the corresponding |
---|
83 | changeset will be shown (same effect as clicking on the !ChangeSet number). |
---|
84 | |
---|
85 | == Alternative Formats == |
---|
86 | |
---|
87 | === The !ChangeLog Text === |
---|
88 | |
---|
89 | At the bottom of the page, there's a ''!ChangeLog'' link |
---|
90 | that will show the range of revisions as currently shown, |
---|
91 | but as a simple text, matching the usual conventions for |
---|
92 | !ChangeLog files. |
---|
93 | |
---|
94 | === RSS Support === |
---|
95 | |
---|
96 | The revision log also provides a RSS feed to monitor the changes. |
---|
97 | To subscribe to a RSS feed for a file or directory, open its |
---|
98 | revision log in the browser and click the orange 'XML' icon at the bottom |
---|
99 | of the page. For more information on RSS support in Trac, see TracRss. |
---|
100 | |
---|
101 | ---- |
---|
102 | See also: TracBrowser, TracChangeset, TracGuide |
---|