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 |
| 15 | * Timestamp — When the changeset was commited |
| 16 | * Author — Who commited the changeset |
| 17 | * Message — A brief description from the author (the commit log message) |
| 18 | * Location — Parent directory of all files affected by this changeset |
| 19 | * Files — A list of files affected by this changeset |
31 | | * Green: Added |
32 | | * Red: Removed |
33 | | * Yellow: Modified |
34 | | * Blue: Copied |
35 | | * Gray: Moved |
36 | | |
| 25 | [[span(style=background:#bfb;border:1px solid #999;font-size:80%;margin-right:.5em,'' '')]] Green: Added \\ |
| 26 | [[span(style=background:#f88;border:1px solid #999;font-size:80%;margin-right:.5em,'' '')]] Red: Removed \\ |
| 27 | [[span(style=background:#fd8;border:1px solid #999;font-size:80%;margin-right:.5em,'' '')]] Yellow: Modified \\ |
| 28 | [[span(style=background:#88f;border:1px solid #999;font-size:80%;margin-right:.5em,'' '')]] Blue: Copied \\ |
| 29 | [[span(style=background:#ccc;border:1px solid #999;font-size:80%;margin-right:.5em,'' '')]] Gray: Moved \\ |
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. |
| 36 | * 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 indicate the exact position of the change in both the old and the new version of the file. |
| 37 | * The ''side-by-side'' style shows the old version on the left and the new version on the right and 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), and modified regions will have a yellow background. |
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 | | |
| 40 | * You can set how many lines are displayed before and after every change; if the value ''all'' is used, then the full file will be shown. |
| 41 | * You can toggle whether blank lines, case changes and white space changes are ignored, thereby letting you find the functional changes more quickly. |
69 | | A very frequent need is to look at changes made on a file |
70 | | or on a directory spanning multiple revisions. |
71 | | The easiest way to get there is from the TracRevisionLog, |
72 | | where one can select the '''old''' and the '''new''' revisions |
73 | | of the path being examined, and then click the ''View changes'' |
74 | | button. |
| 53 | Often you want to look at changes made on a file or on a directory spanning multiple revisions. The easiest way to get there is from the TracRevisionLog, where you can select the ''old'' and the ''new'' revisions of the file or directory, and then click the ''View changes'' button. |
78 | | One of the main feature of source configuration management |
79 | | systems is the possibility to work simultaneously on alternate |
80 | | ''Lines of Developments'', or ''branches''. |
81 | | The evolution of branches are often made in parallel, making it |
82 | | sometimes difficult to understand the exact set of differences |
83 | | between alternative versions. |
| 57 | One of the core features of version control systems is the possibility to work simultaneously on different ''Lines of Developments'', commonly called “branches”. Trac enables you to examine the exact differences between such branches. |
90 | | The resulting set of differences consist in the changes |
91 | | that should be applied to the ''From:'' content in order |
92 | | to make it look like the ''To:'' content. |
93 | | |
94 | | For convenience, it is possible to invert the roles |
95 | | of the '''old''' and the '''new''' path/revision pairs |
96 | | by clicking the ''Reverse Diff'' link on the changeset page. |
| 61 | For convenience, it is possible to invert the roles of the ''old'' and the ''new'' path/revision pairs by clicking the ''Reverse Diff'' link on the changeset page. |
104 | | This shows the last change that happened on that path. |
105 | | The links ''Previous Changeset'' and ''Next Changeset'' |
106 | | are replace by links to ''Previous Change'' and ''Next Change'', |
107 | | which makes it really convenient to traverse the change history |
108 | | of a specific file or directory. |
109 | | This view of a changeset, restricted to a specific path, |
110 | | is called ''restricted changeset''. |
111 | | |
112 | | Of course, if one is doing that on the root of the |
113 | | repository, there will be no path restriction |
114 | | and the full changeset will be shown. |
115 | | |
| 67 | This link will take you to the last change that was made on that path. From there, you can use the ''Previous Change'' and ''Next Change'' links to traverse the change history of the file or directory. |