Changes between Version 2 and Version 3 of TracRevisionLog


Ignore:
Timestamp:
Apr 24, 2017, 10:36:27 AM (2 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracRevisionLog

    v2 v3  
    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.
     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.
    85
    96== 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 latest 100 revisions.
    1912
    2013Also, there 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 corresponding to what has been done on the 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
     17It is also possible to indicate that one wants to see what happened before a ''Copy'' or ''Rename'' change, by selecting the
    3018''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.
     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 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.
    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 also 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
    4627== 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
    5031    for selecting the ''old'' and the ''new'' revisions that will be
     
    5637 1. The '''Revision''' number, displayed as `@xyz`.
    5738    This is a link to the TracBrowser, using the displayed revision as the base line.
    58  1. The '''Changeset''' number, displayed as `[xyz]`.
    59     This is a link to the TracChangeset view.
     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.
    6040 1. The '''Date''' at which the change was made.
    6141    The date is displayed as the time elapsed from the date of the revision. The time
     
    6949== Inspecting Changes Between Revisions ==
    7050
    71 The ''View changes...'' buttons (placed above and below the list
    72 of changes, on the left side) will show the set of differences
    73 corresponding to the aggregated changes starting from the ''old''
    74 revision (first radio-button) to the ''new'' revision (second
     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
    7553radio-button), in the TracChangeset view.
    7654
    77 Note that the ''old'' revision doesn't need to be actually
    78 ''older'' than the ''new'' revision: it simply gives a base
    79 for the diff. It's therefore entirely possible to easily
    80 generate a ''reverse diff'', for reverting what has been done
     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
    8157in the given range of revisions.
    8258
    83 Finally, if the two revisions are identical, the corresponding
    84 changeset will be shown (same effect as clicking on the !ChangeSet number).
     59Finally, if the two revisions are identical, the corresponding changeset will be shown. This has the same effect as clicking on the !ChangeSet number.
    8560
    8661== Alternative Formats ==
     
    8863=== The !ChangeLog Text ===
    8964
    90 At the bottom of the page, there's a ''!ChangeLog'' link
    91 that will show the range of revisions as currently shown,
    92 but as a simple text, matching the usual conventions for
    93 !ChangeLog files.
     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.
    9466
    9567=== RSS Support ===
    9668
    97 The revision log also provides a RSS feed to monitor the changes.
    98 To subscribe to a RSS feed for a file or directory, open its
    99 revision log in the browser and click the orange 'XML' icon at the bottom
    100 of the page. For more information on RSS support in Trac, see TracRss.
     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.
    10171
    10272----