Changes between Version 4 and Version 5 of TracRevisionLog


Ignore:
Timestamp:
Aug 1, 2023, 3:35:37 PM (17 months 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 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.
     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.
    55
    6 == The Revision Log Form ==
     6== The Revision Log Form
    77
    8 It 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. 
     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.
    99
    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 latest 100 revisions.
     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.
    1212
    13 Also, there are three modes of operation of the revision log.
     13There are three modes of operation of the revision log.
    1414
    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 corresponding to what 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.
    1616
    17 It 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.
     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.
    1919Each 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.
    2020
    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 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.
     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.
    2323
    24 Finally, there's also a checkbox ''Show full log messages'', 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
    2525should be displayed for each change, or only a shortened version of it.
    2626
    27 == The Revision Log Information ==
     27== The Revision Log Information
    2828
    2929For 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].
     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].
    3332 1. A color code (similar to the one used for the
    34     [wiki:TracChangeset#ChangesetHeader changesets]) indicating kind of change.
     33    [TracChangeset#ChangesetHeader changesets]) indicates the kind of change.
    3534    Clicking on this column refreshes the revision log so that it restarts
    3635    with this change.
    … …  
    3837    This is a link to the TracBrowser, using the displayed revision as the base line.
    3938 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.
     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.
    4343 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'' 
     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''
    4646    checkbox in the form above.
    47    
    4847
    49 == Inspecting Changes Between Revisions ==
     48== Inspecting Changes Between Revisions
    5049
    5150The ''View changes...'' buttons (placed above and below the list of changes, on the left side) will show the set of differences
    … …  
    5756in the given range of revisions.
    5857
    59 Finally, if the two revisions are identical, the corresponding changeset will be shown. This has the 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.
    6059
    61 == Alternative Formats ==
     60== Alternative Formats
    6261
    63 === The !ChangeLog Text ===
     62=== The !ChangeLog Text
    6463
    6564At 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.
    6665
    67 === RSS Support ===
     66=== RSS Support
    6867
    69 The revision log also provides a RSS feed to monitor the changes. To subscribe to a RSS feed for a file or directory, open its
     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
    7069revision 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.
    7170
    7271----
    73 See also: TracBrowser, TracChangeset, TracGuide
     72See also: TracBrowser, TracChangeset