Changes between Initial Version and Version 1 of TracRevisionLog

10/15/12 16:41:02 (10 years ago)



  • TracRevisionLog

    v1 v1  
     1= Viewing Revision Logs = 
     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. 
     9== The Revision Log Form == 
     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.  
     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. 
     20Also, there are three modes of operation of the revision log. 
     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. 
     28It's also possible to indicate that one wants to see what happened 
     29before a ''Copy'' or ''Rename'' change, by selecting the  
     30''Follow copies'' mode. This will cross all copies or renames changes. 
     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. 
     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. 
     42Finally, there's also a checkbox ''Show full log messages'', 
     43which controls whether the full content of the commit log message 
     44should be displayed for each change, or only a shortened version of it. 
     46== The Revision Log Information == 
     48For each revision log entry, there are 7 columns: 
     49 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]. 
     52 1. A color code (similar to the one used for the 
     53    [wiki:TracChangeset#ChangesetHeader changesets]) indicating kind of change. 
     54    Clicking on this column refreshes the revision log so that it restarts 
     55    with this change. 
     56 1. The '''Revision''' number, displayed as `@xyz`. 
     57    This is a link to the TracBrowser, using the displayed revision as the base line. 
     58 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. 
     62 1. The '''Author''' of the change. 
     63 1. The '''Log Message''', which contains either the truncated or full commit  
     64    log message, depending on the value of the ''Show full log messages''  
     65    checkbox in the form above. 
     68== Inspecting Changes Between Revisions == 
     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 
     74radio-button), in the TracChangeset view. 
     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 
     80in the given range of revisions. 
     82Finally, if the two revisions are identical, the corresponding 
     83changeset will be shown (same effect as clicking on the !ChangeSet number). 
     85== Alternative Formats == 
     87=== The !ChangeLog Text === 
     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. 
     94=== RSS Support === 
     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. 
     102See also: TracBrowser, TracChangeset, TracGuide