Changes between Version 5 and Version 6 of TracRevisionLog


Ignore:
Timestamp:
03/24/15 23:15:03 (3 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracRevisionLog

    v5 v6  
    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.
     4When you browse the repository, it's always possible to query the
     5''Revision Log'' view corresponding to the path you're currently seeing.
     6This will display a list of the most recent changesets in which the
     7current path or any other path below it has been modified.
    58
    69== The Revision Log Form ==
    710
    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.
     11It's possible to set the revision at which the revision log should
     12start, using the ''View log starting at'' field. An empty value
     13or a value of ''head'' is taken to be the newest changeset.
    914
    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.
     15It's also possible to specify the revision at which the log should
     16stop, using the ''back to'' field. By default, it's left empty,
     17which means the revision log will stop as soon as 100 revisions have
     18been listed.
    1219
    1320Also, there are three modes of operation of the revision log.
    1421
    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.
     22By default, the revision log ''stops on copy'', which means that
     23whenever an ''Add'', ''Copy'' or ''Rename'' operation is detected,
     24no older revision will be shown. That's very convenient when working
     25with branches, as one only sees the history corresponding to what
     26has been done on the branch.
    1627
    17 It is also possible to indicate that one wants to see what happened before a ''Copy'' or ''Rename'' change, by selecting the
     28It's also possible to indicate that one wants to see what happened
     29before a ''Copy'' or ''Rename'' change, by selecting the
    1830''Follow copies'' mode. This will cross all copies or renames changes.
    19 Each 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.
     31Each time the name of the path changes, there will be an additional
     32indentation level. That way, the changes on the different paths
     33are easily grouped together visually.
    2034
    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.
     35It's even possible to go past an ''Add'' change, in order to see
     36if there has been a ''Delete'' change on that path, before
     37that ''Add''. This mode corresponds to the mode called
     38''Show only adds, moves and deletes''.
     39While quite useful at times, be aware that this operation is quite
     40resource intensive.
    2341
    24 Finally, there's also a checkbox ''Show full log messages'', which controls whether the full content of the commit log message
     42Finally, there's also a checkbox ''Show full log messages'',
     43which controls whether the full content of the commit log message
    2544should be displayed for each change, or only a shortened version of it.
    2645
    2746== The Revision Log Information ==
    2847
    29 For each revision log entry, the following columns are displayed:
     48For each revision log entry, there are 7 columns:
    3049 1. The first column contains a pair of radio buttons and should be used
    3150    for selecting the ''old'' and the ''new'' revisions that will be
     
    4968== Inspecting Changes Between Revisions ==
    5069
    51 The ''View changes...'' buttons (placed above and below the list of changes, on the left side) will show the set of differences
    52 corresponding to the aggregated changes starting from the ''old'' revision (first radio-button) to the ''new'' revision (second
     70The ''View changes...'' buttons (placed above and below the list
     71of changes, on the left side) will show the set of differences
     72corresponding to the aggregated changes starting from the ''old''
     73revision (first radio-button) to the ''new'' revision (second
    5374radio-button), in the TracChangeset view.
    5475
    55 Note that the ''old'' revision doesn't need to be actually ''older'' than the ''new'' revision: it simply gives a base
    56 for the diff. It's therefore entirely possible to easily generate a ''reverse diff'', for reverting what has been done
     76Note that the ''old'' revision doesn't need to be actually
     77''older'' than the ''new'' revision: it simply gives a base
     78for the diff. It's therefore entirely possible to easily
     79generate a ''reverse diff'', for reverting what has been done
    5780in the given range of revisions.
    5881
    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.
     82Finally, if the two revisions are identical, the corresponding
     83changeset will be shown (same effect as clicking on the !ChangeSet number).
    6084
    6185== Alternative Formats ==
     
    6387=== The !ChangeLog Text ===
    6488
    65 At 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.
     89At the bottom of the page, there's a ''!ChangeLog'' link
     90that will show the range of revisions as currently shown,
     91but as a simple text, matching the usual conventions for
     92!ChangeLog files.
    6693
    6794=== RSS Support ===
    6895
    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
    70 revision 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.
     96The revision log also provides a RSS feed to monitor the changes.
     97To subscribe to a RSS feed for a file or directory, open its
     98revision log in the browser and click the orange 'XML' icon at the bottom
     99of the page. For more information on RSS support in Trac, see TracRss.
    71100
    72101----