1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Description of LinCVS</title>
</head>
<body>
<h1>Description CVS</h1>
<p>CVS (concurent version system) is a commandline tool that maintains
the individual states (different versions) of files in a network
(lan (local area network) or wan (wide area network)). Typically,
cvs is installed on a server, the other computers are cvs-clients.
User can independantly checkout files to their local system, hack
away, and commit the changes back onto the server when done. Many
users can work on the same files at a time because cvs recognizes
overlapping changes and notifys the user of these conflicts. This
check is done at commit time, except for the user running update
whenever he likes. So cvs does not require continous network
connection for working with it.</p>
<p>Furtheron cvs has the ability to maintain several project version
trees, merge changes between individual versions into a third
version, as well as returning a detailed list of the project
activities. All in all a complex project maintenance tool, which is
in use in many open source projects throughout the internet.</p>
<h1>Description LinCVS</h1>
<p>LinCVS is a graphical Interface for the cvs client commandline tool
on the Unix, Mac OS X and Windows platform. It allows to load modules from a
server (checkout), create modules on the server (import), as well as
checking the state of directories and individual files or updating
them. Basic operations like add, remove and commit are supported as
matter of course, just like showing the actual differences between
the server version and the local sandbox, graphical display of the
version tree, and manifoldy graphical support of project maintenance.
All actions are logged on the cvs server (configurable via history),
and are therewith comprehensible.</p>
<p>To keep LinCVS independant of the cvs version, LinCVS uses the local
but separat installed cvs and therewith always should work with the
latest version.</p>
<p>After choosing a startup dir, the project-explorer searches the
subdirectories for cvs projects, and displays these on the workbench.
Now all functions on one/many files or whole directories can be
accessed over pulldown menues or simply a right mouseclick. The state
of the individual directories is continuously scanned by LinCVS. This
means the symbol of the dir tells the user that there are for example
still uncommited changes somewhere in the depth of a dir hierarchy,
even without having opened them yet. So the project state is visualized
right after a cvs status call. Completed with on-the-fly dir scanning,
LinCVS is qualified for large projects with many thousand files.
Because of the continuous efforts of network administrators, to
encrease network security, LinCVS supports all standard cvs connection
protocols. Proxy support is also available, this requires a patched cvs.
This is of course available on our download page.</p>
<p>Because LinCVS does not affect the cvs internal project maintenance, a
concurrent use with cvs commandline is possible. The function of the
LinCVS dir state display is not impaired therewith.</p>
<p>Even though LinCVS graphically supports almost the whole cvs range of
functions (and is continuously under development;-), it is easy to
customize the GUI to the individual needs. Popup menues are freely
configurable, while the menues always provide full feature access. An
extra toolbar enables direct access to often used features.</p>
<p>In contrast to other programs this one is <b>really</b> easy to use ;-) .</p>
<h2>Feature list</h2>
LinCVS supports graphical:<br><br>
Connect methods:
<ul>
<li>local/nfs</li>
<li>pserver</li>
<li>ssh</li>
<li>ssh-agent</li>
<li>proxy</li>
</ul>
Special dirview features:
<ul>
<li>dir-state track keeping</li>
<li>disable/enable tree/dir</li>
<li>continuous dir state monitoring</li>
<li>on-the-fly dir scanning</li>
<li>open dir browser</li>
<li>open shell</li>
<li>expand all</li>
<li>collaps all</li>
</ul>
Overall features:
<ul>
<li>user/server profiles</li>
<li>handle multiple projects simultaneously</li>
<li>ascii/binary file support</li>
<li>project properties</li>
<li>per project settings</li>
<li>reset/update to dir branch</li>
<li>rename file/s</li>
<li>user definable look and feel</li>
<li>user definable icons/icon dir</li>
<li>Application dir installation</li>
<li>import binary/ascii preview</li>
<li>browse modules on server, even without modules file</li>
<li>view files without checkout, from history or log</li>
<li>branch/tag/project-name/commit-info history</li>
<li>tabbed view for cvs-controled/cvs-ignored/non-cvs files</li>
<li>remove files local/in repository/both</li>
<li>open with (startup option for just opening a specific dir)</li>
<li>create new file/dir</li>
<li>internal diff viewer</li>
<li>internal conflict resolver dialog</li>
<li>use of external: editor/browser/shell/diff/remote shell</li>
<li>per project autoupdate status/query update/update feature</li>
<li>debug log function</li>
<li>online help</li>
<li>rename project (in sandbox)</li>
<li>export current (modified) project state</li>
<li>sub-project support (one dir tree with several cvs-projects)</li>
<li>customizable popup menues</li>
<li>customizable key shortcuts</li>
<li>customizable file mapping, separtely for 'open' and 'view'</li>
<li>syntax highlighting</li>
</ul>
cvs features:
<ul>
<li>checkout (branch/tag/date)</li>
<li>import</li>
<li>export (branch/tag/date)</li>
<li>release/remove</li>
<li>status</li>
<li>query update</li>
<li>show editors</li>
<li>show watchers</li>
<li>watch add/remove</li>
<li>edit</li>
<li>unedit</li>
<li>history</li>
<li>commit</li>
<li>tag (add/remove/move/reset)</li>
<li>branch</li>
<li>update (to whatever revision)</li>
<li>login/logout</li>
<li>lock/unlock dir/files</li>
<li>log (graphical zoomable file revision tree)</li>
<li>diff (to repository)</li>
<li>visit file (from log tree or history)</li>
<li>diff and merge (from log tree)</li>
<li>create patch (from log tree)</li>
<li>merge diff between rev1,rev2 into rev3(from log tree)</li>
<li>annotate (with mult. filter functions)</li>
<li>commit info templates</li>
<li>.cvsignore support (global/local/environment/per directory)</li>
<li>add ascii/binary</li>
<li>readd (resurrect) files</li>
</ul>
There are definitelly more (all those we forgot;-),
and LinCVS is still under development ...
</body>
</html>
|
