source: wiki/pages/TracRevisionLog @ 40542

Last change on this file since 40542 was 40542, checked in by obi, 7 years ago

reset wiki files

File size: 4.5 KB
Line 
1= Viewing Revision Logs =
2[[TracGuideToc]]
3
4When you browse the repository, it is always possible to view the ''Revision Log'' that corresponds to the repository path. This displays a list of the most recent changesets in which the current path or any other path below it has been modified.
5
6== The Revision Log Form ==
7
8It is possible to set the revision at which the revision log should start, using the ''View log starting at'' field. An empty value or a value of ''head'' is interpreted as the newest changeset.
9
10It is also possible to specify the revision at which the log should stop, using the ''Back to'' field. By default it is empty,
11which means the revision log will show the latest 100 revisions.
12
13Also, there are three modes of operation of the revision log.
14
15By 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 corresponding to what has been done on the branch.
16
17It is also possible to indicate that one wants to see what happened before a ''Copy'' or ''Rename'' change, by selecting the
18''Follow copies'' mode. This will cross all copies or renames changes.
19Each 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.
20
21It is even possible to go past an ''Add'' change, in order to see if there has been a ''Delete'' change on that path, before
22that ''Add''. This mode corresponds to the mode called ''Show only adds, moves and deletes''. This operation can be quite resource intensive and therefore take some time to be shown on screen.
23
24Finally, there's also a checkbox ''Show full log messages'', which controls whether the full content of the commit log message
25should be displayed for each change, or only a shortened version of it.
26
27== The Revision Log Information ==
28
29For 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
32    used for [wiki:TracRevisionLog#viewingtheactualchanges viewing the actual changes].
33 1. A color code (similar to the one used for the
34    [wiki:TracChangeset#ChangesetHeader changesets]) indicating kind of change.
35    Clicking on this column refreshes the revision log so that it restarts
36    with this change.
37 1. The '''Revision''' number, displayed as `@xyz`.
38    This is a link to the TracBrowser, using the displayed revision as the base line.
39 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.
40 1. The '''Date''' at which the change was made.
41    The date is displayed as the time elapsed from the date of the revision. The time
42    elapsed is displayed as the number of hours, days, weeks, months, or years.
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''
46    checkbox in the form above.
47   
48
49== Inspecting Changes Between Revisions ==
50
51The ''View changes...'' buttons (placed above and below the list of changes, on the left side) will show the set of differences
52corresponding to the aggregated changes starting from the ''old'' revision (first radio-button) to the ''new'' revision (second
53radio-button), in the TracChangeset view.
54
55Note that the ''old'' revision doesn't need to be actually ''older'' than the ''new'' revision: it simply gives a base
56for the diff. It's therefore entirely possible to easily generate a ''reverse diff'', for reverting what has been done
57in the given range of revisions.
58
59Finally, if the two revisions are identical, the corresponding changeset will be shown. This has the same effect as clicking on the !ChangeSet number.
60
61== Alternative Formats ==
62
63=== The !ChangeLog Text ===
64
65At the bottom of the page, there's a ''!ChangeLog'' link that will show the range of revisions as currently shown, but as a simple text, matching the usual conventions for !ChangeLog files.
66
67=== RSS Support ===
68
69The revision log also provides a RSS feed to monitor the changes. To subscribe to a RSS feed for a file or directory, open its
70revision 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.
71
72----
73See also: TracBrowser, TracChangeset, TracGuide
Note: See TracBrowser for help on using the repository browser.