Navigation

Changes between Version 4 and Version 5 of TracRevisionLog


Ignore:
Timestamp:
May 18, 2019, 3:54:44 PM (5 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracRevisionLog

    v4 v5  
    1 = Viewing Revision Logs =
     1= Viewing Revision Logs
    22[[TracGuideToc]]
    33
    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.
     4Each path in the //Repository Browser// contains a contextual navigation link to the //Revision Log//. The //Revision Log// displays a list of the most recent changesets in which the current path or any other path below it has been modified.
    85
    9 == The Revision Log Form ==
     6== The Revision Log Form
    107
    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.
     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.
    149
    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.
     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 [TracIni#revisionlog-default_log_limit-option default log limit], which defaults to the latest 100 revisions.
    1912
    20 Also, there are three modes of operation of the revision log.
     13There are three modes of operation of the revision log.
    2114
    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.
     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 for that branch.
    2716
    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.
     17It 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.
     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.
    3420
    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.
     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 is labeled ''Show only adds, moves and deletes''. The operation can be quite resource intensive and therefore take some time to display.
    4123
    42 Finally, there's also a checkbox ''Show full log messages'',
    43 which controls whether the full content of the commit log message
     24Finally, there's a checkbox ''Show full log messages'', which controls whether the full content of the commit log message
    4425should be displayed for each change, or only a shortened version of it.
    4526
    46 == The Revision Log Information ==
     27== The Revision Log Information
    4728
    48 For each revision log entry, there are 7 columns:
     29For each revision log entry, the following columns are displayed:
    4930 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].
     31    for selecting the ''old'' and the ''new'' revisions that will be used for [#InspectingChangesBetweenRevisions viewing the actual changes].
    5232 1. A color code (similar to the one used for the
    53     [wiki:TracChangeset#ChangesetHeader changesets]) indicating kind of change.
     33    [TracChangeset#ChangesetHeader changesets]) indicates the kind of change.
    5434    Clicking on this column refreshes the revision log so that it restarts
    5535    with this change.
    … …  
    5737    This is a link to the TracBrowser, using the displayed revision as the base line.
    5838 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.
     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.
    6243 1. The '''Author''' of the change.
    6344 1. The '''Log Message''', which contains either the truncated or full commit
    6445    log message, depending on the value of the ''Show full log messages''
    6546    checkbox in the form above.
    66    
    6747
    68 == Inspecting Changes Between Revisions ==
     48== Inspecting Changes Between Revisions
    6949
    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
     50The ''View changes...'' buttons (placed above and below the list of changes, on the left side) will show the set of differences
     51corresponding to the aggregated changes starting from the ''old'' revision (first radio-button) to the ''new'' revision (second
    7452radio-button), in the TracChangeset view.
    7553
    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
     54Note that the ''old'' revision doesn't need to be actually ''older'' than the ''new'' revision: it simply gives a base
     55for the diff. It's therefore entirely possible to easily generate a ''reverse diff'', for reverting what has been done
    8056in the given range of revisions.
    8157
    82 Finally, if the two revisions are identical, the corresponding
    83 changeset will be shown (same effect as clicking on the !ChangeSet number).
     58Finally, if the two revisions are identical, the corresponding changeset will be shown. This has the same effect as clicking on the changeset number.
    8459
    85 == Alternative Formats ==
     60== Alternative Formats
    8661
    87 === The !ChangeLog Text ===
     62=== The !ChangeLog Text
    8863
    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.
     64At 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.
    9365
    94 === RSS Support ===
     66=== RSS Support
    9567
    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.
     68The revision log also provides an RSS feed to monitor the changes. To subscribe to an RSS feed for a file or directory, open its
     69revision 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.
    10070
    10171----
    102 See also: TracBrowser, TracChangeset, TracGuide
     72See also: TracBrowser, TracChangeset