root/projects/WinDictator/trunk/doc/TracChangeset

Revision 19, 4.5 kB (checked in by edsuom, 1 year ago)

Importing windictator into the global FOSS repo

Line 
1 = Trac Changeset Module =
2 [[TracGuideToc]]
3
4 Trac has a built-in functionality for visualizing “diffs” - changes to files.
5
6 There are different kinds of ''change sets''.
7 Some can correspond to revisions made in the repositories,
8 others can aggregate changes made in several revisions,
9 but in the end, any kind of differences can be shown.
10
11 The changeset view consists of two parts, the ''header''
12 and the ''diff views''.
13
14 == Changeset Header ==
15
16 The header shows an overview of the whole changeset.
17 Here you will find information such as:
18
19  * Timestamp -- When the changeset was commited
20  * Author -- Who commited the changeset
21  * Message -- A brief description from the author (the commit log message)
22  * Files -- A list of files affected by this changeset
23
24 If more than one revision is involved in the set of changes being
25 displayed, the ''Timestamp'', ''Author'' and ''Message'' fields
26 won't be shown.
27
28 In front of each listed file, you'll find  a colored rectangle. The color
29 indicates how the file is affected by the changeset.
30  
31  * Green: Added
32  * Red: Removed
33  * Yellow: Modified
34  * Blue: Copied
35  * Gray: Moved
36
37 The color legend is located below the header as a reminder.
38
39 == Diff Views ==
40
41 Below the header is the main part of the changeset, the diff view. Each file is shown in a separate section, each of which will contain only the regions of the file that are affected by the changeset. There are two different styles of displaying the diffs: ''inline'' or ''side-by-side'' (you can switch between those styles using the preferences form):
42
43  * The ''inline'' style shows the changed regions of a file underneath each other. A region removed from the file will be colored red, an added region will be colored green. If a region was modified, the old version is displayed above the new version. Line numbers on the left side indicate the exact position of the change in both the old and the new version of the file.
44  * The ''side-by-side'' style shows the old version on the left and the new version on the right (this will typically require more screen width than the inline style.) Added and removed regions will be colored in the same way as with the inline style (green and red, respectively), but modified regions will have a yellow background.
45
46 In addition, various advanced options are available in the preferences form for adjusting the display of the diffs:
47  * You can set how many lines are displayed before and after every change
48    (if the value ''all'' is used, then the full file will be shown)
49  * You can toggle whether blank lines, case changes and white space changes are ignored, thereby letting you find the functional changes more quickly
50
51
52 == The Different Ways to Get a Diff ==
53
54 === Examining a Changeset ===
55
56 When viewing a repository check-in, such as when following a
57 changeset [wiki:TracLinks link] or a changeset event in the
58 [wiki:TracTimeline timeline], Trac will display the exact changes
59 made by the check-in.
60
61 There will be also navigation links to the ''Previous Changeset''
62 to and ''Next Changeset''.
63
64 === Examining Differences Between Revisions ===
65
66 Often you'll want to look at changes made on a file
67 or on a directory spanning multiple revisions. The easiest way
68 to get there is from the TracRevisionLog, where you can select
69 the ''old'' and the ''new'' revisions of the file or directory, and
70 then click the ''View changes'' button.
71
72 === Examining Differences Between Branches ===
73
74 One of the core features of version control systems is the possibility
75 to work simultaneously on different ''Lines of Developments'', commonly
76 called “branches”. Trac enables you to examine the exact differences
77 between such branches.
78
79 Using the '''View changes ...''' button in the TracBrowser allows you to enter
80 ''From:'' and ''To:'' path/revision pairs. The resulting set of differences consist
81 of the changes that should be applied to the ''From:'' content in order
82 to get to the ''To:'' content.
83
84 For convenience, it is possible to invert the roles of the ''old'' and the ''new''
85 path/revision pairs by clicking the ''Reverse Diff'' link on the changeset page.
86
87 === Checking the Last Change ===
88
89 The last possibility for examining changes is to use the ''Last Change''
90 link provided by the TracBrowser.
91
92 This link will take you to the last change that was made on that path.
93 From there, you can use the ''Previous Change'' and ''Next Change'' links
94 to traverse the change history of the file or directory.
95
96 ----
97 See also: TracGuide, TracBrowser
Note: See TracBrowser for help on using the browser.