Source

XML-CompareML / examples / scm-comparison.output.html

Full commit
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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Version Control System Comparison</title>
<style type="text/css">
h2 { background-color : #98FB98; /* PaleGreen */ }
h3 { background-color : #FFA500; /* Orange */ }
table.compare 
{
    margin-left : 1em;
    margin-right : 1em; 
    width: 90%;
    max-width : 40em;
}
.compare td 
{ 
    border-color : black; border-style : solid ; border-width : thin;
    vertical-align : top;
    padding : 0.2em;
}
ul.toc
{
    list-style-type : none ; padding-left : 0em;
}
.toc ul
{
    list-style-type : none ; 
    padding-left : 0em; 
    margin-left : 2em;
}
.expl
{
    border-style : solid ; border-width : thin;
    background-color : #E6E6FA; /* Lavender */
    border-color : black;
    padding : 0.3em;
}
a:hover { background-color : yellow }
tt { color : #8A2BE2 /* The BlueViolet Color */ }
</style>
</head>
<body>
<h1 id="main">Version Control System Comparison</h1>
<p class="expl">
        This is a comparison of version-control systems. It is split
        into several categories and sub-categories under which the 
        systems are checked.
    </p>
<p>
<b>Timestamp:</b>
<tt>
            $Id: scm-comparison.xml 313 2008-07-12 07:25:40Z shlomif $
        </tt>
</p>
<ul class="toc">
<li>
<a href="#repos_operations">Repository Operations</a>
<ul>
<li>
<a href="#atomic_commits">Atomic Commits</a>
</li>
<li>
<a href="#move">Files and Directories Moves or Renames</a>
</li>
<li>
<a href="#intelligent_renames">Intelligent Merging after Moves or Renames</a>
</li>
<li>
<a href="#copy">File and Directories Copies</a>
</li>
<li>
<a href="#repos_clone">Remote Repository Replication</a>
</li>
<li>
<a href="#push">Propagating Changes to Parent Repositories</a>
</li>
<li>
<a href="#permissions">Repository Permissions</a>
</li>
<li>
<a href="#changesets">Changesets' Support</a>
</li>
<li>
<a href="#annotate">Tracking Line-wise File History</a>
</li>
</ul>
</li>
<li>
<a href="#features">Features</a>
<ul>
<li>
<a href="#work_on_dir">Ability to Work only on One Directory of the Repository</a>
</li>
<li>
<a href="#tracking_uncommited_changes">Tracking Uncommited Changes</a>
</li>
<li>
<a href="#per_file_commit_messages">Per-File Commit Messages</a>
</li>
</ul>
</li>
<li>
<a href="#technical_status">Technical Status</a>
<ul>
<li>
<a href="#documentation">Documentation</a>
</li>
<li>
<a href="#ease_of_deployment">Ease of Deployment</a>
</li>
<li>
<a href="#command_set">Command Set</a>
</li>
<li>
<a href="#networking">Networking Support</a>
</li>
<li>
<a href="#portability">Portability</a>
</li>
</ul>
</li>
<li>
<a href="#user_interaces">User Interfaces</a>
<ul>
<li>
<a href="#web_interface">Web Interface</a>
</li>
<li>
<a href="#availability_of_guis">Availability of Graphical User-Interfaces.</a>
</li>
</ul>
</li>
<li>
<a href="#license">License</a>
</li>
</ul>
<h2 id="repos_operations">Repository Operations</h2>
<h3 id="atomic_commits">Atomic Commits</h3>
<p class="expl">
                Support for atomic commits means that if an
                operation on the repository is interrupted
                in the middle, the repository will not be
                left in an inconsistent state. Are the
                check-in operations atomic, or can
                interrupting an operation leave the
                repository in an intermediate state?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">No. CVS commits are not atomic.</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">Yes. Commits are atomic</td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes (but need to verify)</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">Yes. Commits (checkins) are atomic.</td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">Yes. Commits and updates are atomic.</td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">Commits are atomic.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">Yes. Commits are atomic.</td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">No. VSS commits are not atomic.</td>
</tr>
</table>
<h3 id="move">Files and Directories Moves or Renames</h3>
<p class="expl">
                Does the system support moving a file or directory to
                a different location while still retaining the history
                of the file? <b>Note:</b> also see the next section
                about intelligent merging of renamed paths.
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    No. Renames are not supported and a manual one
                    may break history in two.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Yes. Renames of both files and directories are supported.
                    Supports controlling of symbolic links as well.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">Yes. Renames are supported for files and directories.</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Yes. Directories are first-class controlled entities
                  in Clearcase. Even supports controlling of
                  symbolic/hard links.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">Yes. Both moves and renames are supported, while maintaining history.</td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Renames of files are supported. 
                    Renaming a directory requires creating a new one, 
                    moving the files and deleting the old one. 
                    Moved file histories are preserved.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">
                    Renames are supported for most practical
                    purposes.  Git even detects renames when a file has been
                    changed afterward the rename.  However, due to a peculiar
                    repository structure, renames are not recorded
                    explicitly, and Git has to deduce them (which works well
                    in practice).
                </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                    Yes. Renames and move are supported but the working copy
                    needs to be up-to-date before doing a rename/move operation. 
                    This operation will be committed directly.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">Yes. Renames are supported</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Not directly (you copy and then delete but it manages to 
                    keep track of the branch)
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Yes. File renames are directly supported. File and folder 
                    moves require creating a new one and deleting the old one. 
                    Moved file histories are preserved.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Yes. Both moves and renames are supported, while maintaining history.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">No. Renames are not supported.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes. Renames are supported.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  Yes. Both moves and renames are supported,
                  while maintaining history.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Yes.  The unit of checkout/checkin is a directory
                    tree.  Files and directories can be added,
                    deleted, and renamed between versions.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    Affects the whole history, it's like renaming a 
                    file in the CVS repository. There is a kludgy workaround 
                    using "share-rename,move,delete" that gets what you 
                    want.
                </td>
</tr>
</table>
<h3 id="intelligent_renames">Intelligent Merging after Moves or Renames</h3>
<p class="expl">
                If the system keeps tracks of renames, does it support
                intelligent merging of the files in the history after
                the rename? (For example, changing a file in a renamed
                directory, and trying to merge it).
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    Renames are not supported at all, much less intelligent
                    ones.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Unknown. FILL IN.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">Yes. Renames can be merged intelligently.</td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">Yes. Renames are intelligent.</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Probably Yes.</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">Unknown. FILL IN.</td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">
                    Unkown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">Unknown.</td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">
                    As detailed in the <a href="http://git.or.cz/gitwiki/GitFaq#rename-tracking">Git
                        FAQ</a>:
                    "Git has a rename command git mv, but that is just a
                    convenience. The effect is indistinguishable from removing
                    the file and adding another with different name and the
                    same content."
                </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    No. <a href="http://hgbook.red-bean.com/hgbookch5.html#x9-1030005.4">the
                        Mercurial book says:</a>
                    "When you use the 'hg rename' command, Mercurial makes a 
                    copy of each source file, then deletes it and marks the
                    file as removed. "
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Unknown. FILL IN.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">Unknown.</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    No, renames are not intelligent.
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    "svn help me" says "Note: this subcommand is equivalent to 
                    a 'copy' and 'delete'." There's <a href="http://subversion.tigris.org/issues/show_bug.cgi?id=898">a 
                        bug report about it</a>.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">No. Renames are not supported.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Same as Subversion.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Unknown. FILL IN.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    No, renames are not intelligent.
                </td>
</tr>
</table>
<h3 id="copy">File and Directories Copies</h3>
<p class="expl">
                Does the version control system support copying
                files or directories to a different location at the
                repository level, while retaining the history?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">No. Copies are not supported.</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Copying is supported through symbolic links
                    (but all linked files are treated as the same file 
                    version).  Moves are fully supported with the history
                    retained.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">No. Copies are not supported.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">No. Copies of files and directory structures are
                    not supported. 
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">No. Copies are not supported.</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    Yes. Copies are supported.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Yes, through use of hard links. (But some
                  limitations in Windows environments)
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">Yes. An inexpensive operation that can be used for
                    sharing files in multiple places.  On deploy, you have the
                    option of deploying only one of the shared files or all of them.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes, and it's a very cheap operation (update the target
					directory to include the new file/directory).
				</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Copying doesn't retain history, moving does.</td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">No. Copies of files and directory structures are
                    not supported. 
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">No.  Copies are not supported.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">No, copies will start their own history.</td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes. Copies are supported</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Yes. Copies are supported</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">No. Copies are not supported.</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">Copies are supported (though, because
                    of its architecture, I don't know how well)
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">Yes. Copies are supported.</td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Copying doesn't retain history, moving does.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Yes. And it's a very cheap operation (O(1)) that 
                    is also utilized for branching.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">No. Copies are not supported.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes. Same as subversion.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  Yes - you can create a branch. But the GUI has no option to
                  view the old history. The <a href="http://msdn.microsoft.com/en-us/tfs2008/bb980963.aspx">
                  Power-Tool tfpt</a> has the option /followbranches to show
                  the history of the file branch's ancestors
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Yes.  A new package/branch can be based on any
                    existing version without affecting the past
                    history.  (This is also an O(1) operation.)
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">Yes. Copies are supported up to a point.</td>
</tr>
</table>
<h3 id="repos_clone">Remote Repository Replication</h3>
<p class="expl">
                Does the system support cloning a remote repository to get
                a functionally equivalent copy in the local system? That 
                should be done without any special access to the remote 
                server except for normal repository access.
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    Indirectly, by using
                    <a href="http://www.cvsup.org/">CVSup</a> 
                    by John Polstra (which requires running the cvsupd 
                    daemon on the server)
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Not really applicable for clearcase, but see next point.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">Yes. CM+MultiSite can be configured to clone a repository
                    so that it continues to act as a single repository. Options include
                    cloning only from the main site (i.e. not allowing updates from the
                    clone) and restricting the set of files transferred to a cloned site.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes, as long as you have the (more expensive) Distributed package.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Repositories are always replicated on local machines. 
                    There is no central server.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Yes.  This is very intrinsic feature of Git.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Yes, but is not documented and its based on the dataflow feature of the
                  LibreSource Synchronizer.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">Yes. Via the Perforce Proxy (P4P) tool.</td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    No. (But a proxy feature is planned for 
                    inclusion in the next releases.)
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Not directly possible with the included GUI or command line tools; Some SQL Server tool might be useable.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    Indirectly, by using Chia-liang Kao's 
                    <a href="http://search.cpan.org/dist/SVN-Mirror/">SVN::Mirror</a>
                    add-on or Shlomi Fish' 
                    <a href="http://search.cpan.org/dist/SVN-Pusher/">SVN-Pusher</a> 
                    utility.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  TFS Proxy is available but the replica isn't an
                  equivalent copy.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">Yes.  Replication is a fundamental part of the design.</td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    Not directly possible with the included GUI or 
                    command line tools; ssarc and ssrestor might be useable
                </td>
</tr>
</table>
<h3 id="push">Propagating Changes to Parent Repositories</h3>
<p class="expl">
                Can the system propagate changes from one repository to 
                another?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    With AccuReplica, the replica server has all the meta-data 
                    and  fetches file data as needed by replica users; all 
                    write operations pass automatically from the replica to 
                    the master server.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">Yes, using Clearcase Multisite.</td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes.  In CM+MultiSite, changes made at the slave are,
                    by default, propagated to the Main(master) library, as well as
                    to all other Clones (slaves).  You may also propagate changes
                    between unrelated repositories containing some of the same source.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes, as long as you have the (more expensive) Distributed package.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">It's a peer-to-peer system, 
                    which keeps all replicas of the repository in sync.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Yes.  (The Linux kernel development process uses this extremely often).</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">Yes, it's what we call a dataflow.</td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">Unknown. Probably Not.</td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Not directly possible with the included GUI or command line tools; Some SQL Server tool might be useable.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Yes, using either Chia-Ling Kao's SVN::Mirror
                    script or the svn-push utility by Shlomi Fish.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Yes.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    Not directly possible with the included GUI or 
                    command line tools; ssarc and ssrestor might be useable
                </td>
</tr>
</table>
<h3 id="permissions">Repository Permissions</h3>
<p class="expl">
                Is it possible to define permissions on access to different
                parts of a remote repository? Or is access open for all? 
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    Limited. "pre-commit hook scripts" can be used to 
                    implement various permissions systems.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Yes. Access can be defined per stream (branch) using 
                    access control lists.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    Yes. Aegis relies on the UNIX permissions system to
                    implement permissions for files in the repository.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Yes. It is possible to define permissions on access to
                    different parts of a remote repository based on the 
                    permission systems of the underlying protocol.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Basic access control can be implemented through a
                    contributed hook script.  ACL support for the
                    Bazaar server is planned.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    FILL IN
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Yes, a unix-like permissions model is used, which maps
                  onto Windows domain-based authentication in
                  multi-platform environments.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes.  Permissions are defined by data, primarily,
                    not by location.  If location is a part of the data, it may
                    be used to define permissions by location.  Permissions may
                    apply to a branch, file, problem report, test case, etc.
                    Access may be extended based on peer group, manager, and
                    access lists.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">No, though a single server can serve many repositories.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">First access (joining the project) 
                    requires administrator's approval.
                    Subsequent access to that project is not controlled.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    No.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">No, but a single server can serve many repositories.  Also, UNIX permissions can be used to some extent.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">Permissions are set for the whole repository or branch.</td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    Yes. It is possible to lock down repositories,
                    subdirectories, or files using hooks.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Yes. It is possible to restrict incoming changes
                    from certain sources to be performed only in certain
                    parts of the repository.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    Permissions are defined on a per-branch
                    basis.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Yes. (more than half a dozen of permission levels that can 
                    be set in a file by file basis)
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Yes. (more than half a dozen of permission levels that can 
                    be set in a file by file basis)
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Yes. SourceAnywhere Server Manager can define access to a repository per user or group and user access rights to a project.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    Yes. The WebDAV-based service supports defining HTTP
                    permissions for various directories of the repository.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                    No.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">
                    Same as subversion.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  Yes. You get set permissions for each team project, folder,
                  file.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Yes.  Access permissions for each package (the
                    unit of checkout/checkin) can be different.
                    Access permissions for a branch can be different
                    from the basis package.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    Project specific permissions (read, write, delete, destroy)
                    can be set per user; but see "Networking Support":
                    this makes "Repository Permissions" a hindrance to 
                    accidental damage but cannot prevent intentional damage.
                </td>
</tr>
</table>
<h3 id="changesets">Changesets' Support</h3>
<p class="expl">
                Does the repository support changesets? Changesets are a way
                to group a number of modifications that are relevant to each
                other in one atomic package, that can be cancelled or 
                propagated as needed.
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">No. Changes are file-specific.</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Yes, AccuRev provides robust functionality for change 
                    sets (called change packages in AccuRev) including viewing 
                    differences by change packages and merging changes from 
                    stream to stream by change package.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Not supported in this way. Extensive branching
                  support gives similar benefits. (eg each changeset
                  can be given a branch). Also optional UCM feature
                  gives something like this (each changeset is a
                  "stream").
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes. Change packages are known as updates.  By
                    default, an update is required to make any change.  The
                    update may be checked-in, differenced, promoted, retrieved,
                    propagated, yanked (i.e. removed from history), etc. each in
                    a single operation.  Baseline alignment is performed
                    based on the status (i.e. promotion level) of the update.
                    Updates also record changes to directory structure: move,
                    add, remove.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes.  Changesets (or tasks) are fundamental
                	to the way Synergy works.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Yes. Changesets are the default.</td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Yes, Changesets are supported, and there's some flexibility in creating them.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Partial support. There are implicit changeset that are generated on
                  each commit.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Yes. Changesets are supported.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Not exactly. SourceAnywhere uses a related concept of configurations instead, which some has similar properties.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Partial support. There are implicit 
                    changeset that are generated on each commit.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">Partial support. Changes are grouped into changesets,
                    but cannot be cancelled invididually yet.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Same as subversion.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">Yes. Changesets are only possibility.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Not exactly.  Vesta uses a related concept of
                    configurations instead, which some has similar
                    properties.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">No.  Changes are file-specific.</td>
</tr>
</table>
<h3 id="annotate">Tracking Line-wise File History</h3>
<p class="expl">
                Does the version control system have an option to track the
                history of the file line-by-line? I.e., can it show for each line
                at which revision it was most recently changed, and by whom?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">Yes. cvs annotate</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">Yes. Available from both the gui and cli.</td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Yes. aeannotate</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">Not in the command line client, but ViewARCH,
                a web-interface for Arch, has it.</td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">Yes. (bzr annotate).</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes. (bk annotate)</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">Yes, "cleartool annotate"</td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">Yes.  View revision tags. </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Probably, if you're a sufficiently proficient hacker with
					their scripting language.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Not directly, but it's possible to compare 
                    any two versions using a visual differ.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">Yes. (darcs annotate)</td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Yes. (git blame).</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                    Yes, locally without any server connection with the standard graphical
                    Java client.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes. (hg annotate)</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Yes, as of version 0.19.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">Unknown. Probably not.</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">Yes, an annotation feature is present.</td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">Yes, annotation is available through the GUI.</td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Yes. (SAW annotate)</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Yes. (svn blame)</td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes. (svk blame)</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">Yes. (tf annotate).</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    No, but it would be easy to implement a tool that
                    did this, as the Vesta repository provides direct
                    filesystem access to all versions.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">Not directly, but it's possible to compare 
                    any two versions using a visual differ.
                </td>
</tr>
</table>
<h2 id="features">Features</h2>
<h3 id="work_on_dir">Ability to Work only on One Directory of the Repository</h3>
<p class="expl">
                Can the version control system checkout only one directory of
                the repository? Or restrict the check-ins to only one 
                directory?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Yes. AccuRev provides functionality to define
                    feature streams in which only the subset of code is seen.
                    A group of developers can then be retricted to work only
                    from that stream so they are only allowed to check in
                    changes to that subset of code.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">No. All changes are made repository-wide.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    It is possible to commit only a certain directory. 
                    However, one must check out the entire repository as a
                    whole.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">For checkouts: No. For checkins: Yes.</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">No. All changes are made repository-wide.</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">Yes, using snapshot view load rules.</td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes.  Any arbitrary set can be checked out
                    and worked on.  Similarly, arbitrary restrictions may be
                    applied for check-in, including file ownership.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">
                    Yes and no.  Files and directories are checked out and in
                    individually, however you have to work in the context of a 
                    project, which consists of one or more directories.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">No. All changes are made to a project as
                    a unit, but it's possible to access each file's
                    history separately.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    It is possible to commit only a certain directory. 
                    However, one must check out the entire repository as a
                    whole.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">No.  However, commits could be restricted somewhat, see the "Repository Permissions".</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                   It is possible to commit only a certain directory. However, one must
                   check out the entire repository as a whole.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    It is possible to commit changes only in a subset of the
                    tree. There are plans for partial checkouts.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    It is possible to commit changes only in a subset of the
                    tree. However, one must extract the entire tree to work
                    on it.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">No. All changes are made to a project as
                    a unit
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Yes. Changes to a sub-directory of the repository 
                    are supported.
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Yes.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Yes. SourceAnywhere can define the user access right to each project
                 and users can be restricted to work only on the projects they have check out/in right.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Yes and no. The unit of checkout/checkin (called a
                    package) is a directory tree.  Most projects use
                    more than one.  Once created, a package must be
                    checked out/in as a unit.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">Yes.</td>
</tr>
</table>
<h3 id="tracking_uncommited_changes">Tracking Uncommited Changes</h3>
<p class="expl">
                Does the software have an ability to track the changes in the
                working copy that were not yet committed to the repository?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">Yes. Using cvs diff</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Yes. The functionality is available through both the GUI
                    and the command line interface.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Yes. Using aediff</td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Yes. Using aediff.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Yes, using "tla changes".
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">Yes, using "bzr diff".</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes. Using bk diff.</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">Yes, "cleartool diff"</td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes. Use Updates | Delta | Delta Update. Or
                    right click a file or directory and do a compare to workspace.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes, either using integrated diff tool or user-configured
					external diff tool</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Yes, using built-in visual differ/editor.</td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    Yes, using "darcs whatsnew".
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Yes.
                Also, branches are very lightweight in Git, and
                could be considered a kind of storage for "uncommitted" code in some workflows.
                </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Yes, with the Synchronizer Studio (default Java client) or with the
                  standard diff command (diff -r . .so6/xxx/REFCOPY/)
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes. Using hg diff.</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">Yes. In a similar fashion to CVS.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">Yes. Using cm diff</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Yes. Using saw diff.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Yes. Using svn diff</td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">Yes. Local changes are detected and shown immediately. Changes can be
                  collected in a local buffer before being committed to the repository.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes. Using svk diff</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  Yes. Using tf diff or "Pending Changes" in Visual Studio.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Yes.  Intermediate immutable snapshots can be
                    taken during an active checkout (with vadvance).
                    These intermediate versions can be treated just
                    like checked in versions: they can be replicated
                    to other repositories and used as the basis for
                    branches.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">Yes, using integrated diff tool.</td>
</tr>
</table>
<h3 id="per_file_commit_messages">Per-File Commit Messages</h3>
<p class="expl">
                Does the system have a way to assign a per-file commit message
                to the changeset, as well as a per-changeset message?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">No. Commit messages are per change.</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">No. Commit messages are per change.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    No.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    With respect to pure Bazaar: No.  At least one
                    plugin (bzr-gtk) supports it though.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes. It is possible to have a per-file
                    commit message</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Yes, assuming a comment on the branch is sufficient
                  for a per-changeset message.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes.  Out of the box CM+ is configured to
                    prompt for messages (i.e. comments) only per change.
                    However, the schema is pre-configured so that you may
                    prompt on a per file basis as well (typically done at
                    checkout time as the entire change is normally checked
                    in with a single operation.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">No. Commit messages are per change.
                    They go to all project members and update
                    their repositories.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    No.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">No. Commit messages are per changeset.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">No. Commit messages are per changeset.</td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    No.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Yes. It is possible to attach a comment to a certain
                    file at a certain revision.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    Unknown.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    No. Commit messages are per change.
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    No. Commit messages are per change.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">No. There is no such feature.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">No. There is no such feature.</td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">No. There is no such feature.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">No. Commit messages are per changeset.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Not exactly.  The unit of checkin is a directory,
                    and commit messages are assigned at that level,
                    not to individual files.  Since configurations are
                    also versioned, they also have commit messages.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">Since changesets are not supported, yes.</td>
</tr>
</table>
<h2 id="technical_status">Technical Status</h2>
<h3 id="documentation">Documentation</h3>
<p class="expl">
                How well is the system documented? How easy is it to
                get started using it?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">Excellent. There are many online tutorials and 
                    resources and an online book. The command line client
                    also provides an online comprehensive help system.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Excellent.  There is a full set of documentation available 
                    in pdf format available at 
                    <a href="http://www.accurev.com/documentation.html">AccuRev 
                        Documentation</a> as well as context-sensitive help 
                    in the GUI.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    Medium. The documentation is given in several large scope
                    troff documents, that are only usable as not-so-PDFish
                    PDF documents, and as text documents that lack any 
                    formatting. It is very hard to get started using
                    it with the online resources. The content is of good
                    quality, but otherwise not made very accessible.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Medium. There are two online tutorials and a 
                    comprehensive online documentation. The command line
                    client also supplies a reference page. However, some of 
                    the documentation is out of date or incomplete.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Excellent.  Apart from online help in the command
                    line client there exist tutorials, a reference
                    card ("Quick Start Guide"), several full fledged
                    guides and references, and documents on
                    specialized topics, such as migration from other
                    VCS systems and different workflows.  The
                    documentation comes in html and plain-text formats.  The
                    API of the underlying library is fully documented.
                    In the UI design of the command line client
                    special attention was paid to make it easy to get
                    started with Bazaar.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    Very good. There is a comprehensive help at the BitKeeper
                    site. Each command is documented in its own man page, 
                    and the client contains a help tool that offers
                    an integrated help system.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Extensive online help in Windows Help / UNIX manpage
                  format, also PDF-based documentation. However the
                  complexity of the tool can mean a lengthy ramp-up
                  time.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Very good.  There is a self-demo/tutorial
                    to get you started quickly.  Administration is minimal.
                    So normal developer use requires only a 1 to 2 hour
                    training session (or equivalent guide) to introduce you
                    to concepts and capabilities (e.g. like updates, options).
                    Customization documentation is also extensive but should
                    normally be accompanied by a 2-day to 4-day course for
                    GUI, Process, Data and Application set customization.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Medium.  Lots of books, plus somewhat
                	clunky set of HTML pages, but has some radical concepts
                	which can cause real problems really quickly.  They recommend
                	a day's training for basic users, more for more advanced users.
                	Took a while to become fluent.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Very good. Step-by-step tutorial and HTML help
                    is included.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    Good. The manual contains a brief tutorial and a solid
                    reference.  Every sub-command can print its usage.
                    Because the command-set is small and the model is
                    simple, many users find it easy to get started.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">
                 Medium. The short help is too terse and obscure. The man pages are extensive,
                 but tend to be confusing. The are many tutorials.
             </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Medium. There are an online tutorial and some comprehensive online
                  documentation. Installing and getting started with the GUI is very easy
                  though. (update/commit-next-next-next-finished)
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    Very good.  There is a 
                    <a href="http://hgbook.red-bean.com/">companion 
                        book</a> and a wiki. Every command has integrated help.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Good. There's an overview and tutorial written in Texi,
                    and a man page. The client supplies documentation for
                    every command.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    Well documented.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Very Good (html and command line help)
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Very Good (html and command line help)
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Good. There's an overview and tutorial on the web site,
                 and integrated help for every command.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    Very good. There is a free online book and some online
                    tutorials and resources. The book is written in 
                    DocBook/XML and so is convertible to many different 
                    formats. The command-line client also provides a good 
                    online help system that can be used as a reference.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                    Fairly poor. There are two tutorials, but there is no
                    reference. Installing and getting started with the GUI
                    is very easy though.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">
                    Relatively poor, but improving. There's 
                    <a href="http://svkbook.elixus.org/">a work-in-progress 
                        book</a> as well as 
                    <a href="http://svk.elixus.org/">the Wiki</a> and some
                    external Articles and Tutorials.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  Good. A comprehensive documentation in the MSDN Library.
                  Many Step-by-Step tutorial videos online.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Quite thoroughly (HTML, man pages, published
                    papers, a book-length research report).
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">Medium.  Help file which is sometimes useful.
                	However, the interface is reasonably intuitive so
                	documentation isn't needed as much.
                </td>
</tr>
</table>
<h3 id="ease_of_deployment">Ease of Deployment</h3>
<p class="expl">
                How easy is it to deploy the software? What are
                the dependencies and how can they be satisfied?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    Good. Out of being the de-facto standard, 
                    CVS is available on most systems and is easy
                    to deploy.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Excellent.  All that is required is to download the
                    binaries for the appropriate platform and run the
                    installer.  The installation package is self-contained.  No
                    additional software is needed.  AccuRev supports most UNIX,
                    Linux, and Windows platforms and deploying AccuRev to a
                    multi-platform environment is straight-forward.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    The Aegis binary should be installed as SUID-root, and
                    so requires root privileges to install. It also not very
                    portable to Win32 systems. Other than that, Aegis supports
                    an easy autoconf or RPM/apt-based installation process.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Excellent. An arch service is nothing but a 
                    filesystem-space hosted by any of its supported
                    protocols (FTP, SFTP, WebDAV, etc.). The arch client
                    is written in C, and is portable across UNIX systems
                    (and on Win32 only with a UNIX emulation layer).
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Very easy.  Bazaar has an installer for MS Windows
                    and packages for some major Linux distributions,
                    FreeBSD, and Mac OS X.  The dependencies for
                    manual installation are listed on the Bazaar
                    website.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    Good. All that is required is downloading a binary
                    for the system and installing it using the installation
                    script. The package is self-contained and is easy to
                    set up.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Poor. Clearcase is very difficult to install in
                  general. At least, setup for a new site is quite
                  complex. Installing additional servers (eg
                  repository servers) is less so.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes. Typical installation need only be done
                    on the server (with a single shortcut established on the
                    client).  This assumes file system connectivity. For IP
                    only connectivity, installation is also required on
                    remote clients.  Installation is typically a couple of
                    minutes. No dependencies unless web interface is used,
                    in which case an Apache server is required. A download
                    is available from Neuma's web site and takes you right
                    into a self-guided fully working demo version.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">
                    Medium. There is a detailed install guide for setting it
                    up using a binary kit and a set of scripts.  However
                    it still took several tries to get it properly installed
                    and configured.  The Windows client has a slightly clunky
                    Windows installer.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Very easy to deploy, since there is no central
                    server. Can be configured to use e-mail or LAN (or both) for 
                    synchronization. For e-mail, requires MAPI-compliant 
                    e-mail client.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    Very good. darcs requires few external libraries,
                    however you need the Glasgow Haskell Compiler if you
                    cannot find a binary. To start working, just "darcs
                    init".
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">
                   Good.  Binary packages are available
                   for modern platforms.  C compiler and Perl are
                   required. Requires cygwin on Windows, and has some
                   UNIXisms.
               </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Excellent. It is managed by JavaWebStart with links on any
                  LibreSource repository web page. 
                  (links: create workspace, update, commit, studio...)
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    Excellent.  Binary packages are available for all
                    popular platforms.  Building from source requires
                    only Python 2.3 (or later) and a C compiler.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Excellent. It is possible to copy or compile the executable
                    to the user's machine, without any configuration or
                    external dependencies.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    Very good. Install the RPM, or build from tarball and
                    install the init script.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Very good. Perforce is very easy to deploy.
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Very good. PureCM is very easy to deploy.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Excellent. Dynamsoft SourceAnywhere is extremely easy to install.
                 It is totally written in C++ from scratch,
                  which means that you don't need any additional components
                   and frameworks to support the installation.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    A Subversion service requires installing an Apache 2
                    module (if one wishes to use HTTP as the underlying
                    protocol) or its own proprietary server. The client
                    requires only the Subversion-specific logic and the
                    Neon WebDAV library (for HTTP). Installation of the
                    components is quite straightforward, but will require
                    some work, assuming Subversion does not come prepackaged
                    for one's system.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                    If Java 1.4 is installed, deployment of Superversion
                    usually takes two clicks.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">
                    In addition to installing subversion, users are required
                    to install the subversion perl bindings and a few modules
                    from CPAN.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  Installation is quite complex. Needs IIS, MS-SQL Server and
                  Reporting Services. A own installation guide with
                  step-by-step guide is available.
                  Allows separating in data and app tier.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Medium to Good.  There is a detailed installation guide
                    for setting it up using a binary kit.  RPMs and
                    Debian packages have been recently released.
                    There are no dependencies on other software. There is a
                    bootstrap package available to build Vesta from using
                    "make".
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    Very good - an installation package which does the work.
                    When you create a repository it installs the exe's in a 
                    directory and you can run them from there if you need to.
                </td>
</tr>
</table>
<h3 id="command_set">Command Set</h3>
<p class="expl">
                What is the command set? How compatible is it with
                the commands of CVS (the current open-source defacto
                standard)?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    A simple command set that includes three most commonly
                    used commands (cvs commit, cvs update and cvs checkout)
                    and several others.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Very extensive but not compatible with cvs.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    A complex command set that involves many operations
                    just to get started. Not CVS-compatible. (albeit
                    support for such basic operations was contemplated)
                    Note that Aegis is a Software Configuration Management
                    system and not just a simple version control system, 
                    which may justify this extra complexity.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Many commands are compatible with CVS or BitKeeper. However,
                    there are many other commands for it for different uses. 
                    Aliasing of commands is possible so it it may be possible
                    to make it more compatible.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Tries to follow CVS conventions, but deviates
                    where there is a different design.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    A CVS-like command set with some easy-to-get-used-to
                    complications due to its different way of work and 
                    philosophy.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Excellent. All tools are available through the
                  command-line. Not very compatible with CVS though.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                        CM+ has several dozen commands that can
                    be used both for operation and configuration of the product.
                    As CM+ is change-based, commands are substantially
                    different than CVS.  The GUI is used primarily and implemented
                    on top of the command set.  As well, CM+ covers a full ALM
                    suite and can be extended beyond, so there are many more
                    generic commands for browsing, reporting, etc. 
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">An extensive and powerful command set,
                	which has some CVS similarity, though the architecture
                	is so different that it quickly moves away for anything
                	but the basics.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Basic commands are compatible with CVS.</td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    The command set is fairly compact and the core commands
                    are easy to understand.  Follows CVS in a few places,
                    but since the model is different most commands are
                    unique.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Command set is very feature-rich, and not compatible with CVS.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Basic commands available (commit/update), but it's really simple to
                  use the GUI. Ant task are also available.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    Tries to follow CVS conventions, but deviates where there
                    is a different design.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Tries to follow CVS conventions, but deviates where there
                    is a different design.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    A CVS-like command set that is familiar to existing CVS
                    users.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Very extensive but not compatible with CVS.
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    A CVS-like command set which is easy to get used to
                    for CVS-users.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Very extensive but not compatible with CVS.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    A CVS-like command set which is easy to get used to
                    for CVS-users.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                    There is little need to memorize a command set because
                    all actions take place in a GUI. A part of the terminology
                    used in the application is borrowed from CVS.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">
                    A CVS-like command set which is easy to get used to
                    for CVS-users.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                  The command set allows more operations than the GUI
                  but isn't compatible with CVS.
                </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    The command set is unrelated to CVS.  Most of the
                    time, users use about 5 commands.  Few ever need
                    to know more than about 20 commands.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    A bit of an afterthought.  It's possible to do basic
                	things, but it's really geared up for using the GUI.
                </td>
</tr>
</table>
<h3 id="networking">Networking Support</h3>
<p class="expl">
                How good is the networking integration of the system?
                How compliant is it with existing protocols and infra-structure?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    Good. CVS uses a proprietary protocol with various 
                    variations for its client/server protocol. This protocol
                    can be tunneled over an SSH-connection to support 
                    encryption.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Good. (proprietary protocol using TCP/IP)
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    Poor. Aegis is filesystem-oriented and so can be networked
                    only via NFS (network file-system) or a similar protocol.
                    There exists some HTTP-functionality, but it is quite
                    limited.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Excellent. Arch can utilize a multitude of protocols
                    for its service, which is nothing but a dumb remote 
                    filesystem server. Currently supported protocols include
                    FTP, SFTP, WebDAV (remote file access over HTTP), 
                    as well as any remote filesystem protocol (NFS, SMB).
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Excellent. Works natively over HTTP (read-only),
                    FTP and SFTP without having Bazaar installed at
                    the remote end.  Works over HTTP, SSH and a custom
                    protocol when talking to a remote Bazaar
                    server. Supports RSYNC and WebDAV (experimental)
                    through plugins.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    Good. Repositories can be checked out from remote
                    over HTTP, and BitKeeper also sports its own proprietary
                    protocol for communicating between one repository and
                    the other.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Poor. Uses an *extremely* chatty RPC protocol for
                  most clearcase operations, plus NFS or SMB for
                  accessing the files themselves. Typically servers
                  should be deployed locally (ie on the same LAN) as
                  the client workstations for acceptable performance.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Very good.  File system connectivity,
                    TCP/IP connectivity and Web connectivity may be
                    intermixed. MultiSite connectivity is over TCP/IP,
                    as is License server. Works well with SSH, NFS, SMB, etc.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Good (single TCP/IP socket)</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Uses the simplest LAN interface: 
                    copying files between shared directories.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    Good. Darcs supports getting patches over HTTP, and
                    getting and sending patches over SSH and email.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">Excellent.  Can use native Git protocol,
                but works over rsync, ssh, HTTP and HTTPS also.</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Good. Use of HTTP to get through firwalls. 
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    Excellent.  Uses HTTP or ssh.  Remote access also
                    works safely without locks over read-only network
                    filesystems.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Good. Uses a custom protocol called "netsync".
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    Good. Uses its own proprietary client/server protocol.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Good. (single TCP/IP socket)
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Good. (single TCP/IP socket)
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Good. (single TCP/IP socket)</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    Very good. The Subversion service can use either 
                    WebDAV+DeltaV (which is HTTP or HTTPS based) as its 
                    underylying protocol, or its own proprietary protocol
                    that can be channeled over an SSH connection.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                    Good. Network support based on RMI is integrated
                    seamlessly. Encryption and HTTP tunnelling are planned
                    for the near future.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">
                    Very good. svk uses SVN::Mirror to retrieve remote
                    repository. There has been plans to add VCP support
                    to SVN::Mirror so it will be able to mirror from arbitary
                    remote version control systems.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">Good. Use of HTTP(S).</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Networking is inherent to the system.  The
                    repository exports both an NFS interface and an
                    RPC interface.  The checkout and checkin tools
                    automatically contact a remote repository when
                    required to perform an operation.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    VSS uses a Windows network share which has to be writable
                    for the VSS users (since this means doubling maintenance
                    for new users). Add user in VSS and to share permissions. 
                    the share is most often world-writable, as is the default
                    when creating a share) It does not perform well over a 
                    slow network connection.
                </td>
</tr>
</table>
<h3 id="portability">Portability</h3>
<p class="expl">
                How portable is the version-control system to various 
                operating systems, computer architectures, and other
                types of systems?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">
                    Good. Client works on UNIX, Windows and Mac OS.
                    Server works on UNIXes and on Windows with a UNIX
                    emulation layer.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    Excellent. The server runs on most UNIX, Linux 
                    and Windows platforms. The client runs on all of these 
                    platforms and on Mac OS X.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    Medium. The source is portable across all UNIXes,
                    but the Windows version work only using cygwin, and even
                    then not entirely natively.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    Good. The source is portable across all UNIXes,
                    but requires a UNIX emulation layer on Windows. (need to 
                    verify). A service can be hosted on any platform
                    that sports a suitable Internet service.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Works on MS Windows, Linux, Mac OS X, FreeBSD,
                    UNIX, and basically on any system that has a
                    recent Python port.  With case-insensitive file
                    systems there are some issues that can be avoided
                    by using a graphical frontend.  On MS Windows
                    there is a plugin to support tracking of symlinks
                    even if they are not supported natively by the
                    file system.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    Very good. Binaries are available for most common UNIX
                    systems and for Windows 98 and above.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Medium. Available on Windows, and several selected
                  flavours of UNIX (not including MacOS X, or any
                  other Linux other than Red Hat).
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Good.  Clients and Servers work on Unix,
                    Linux, and Windows.  MAC OS X port pending.  Moving server
                    from one platform to another is a copy operation only. Can
                    have different platforms for different servers in a MultiSite
                    configuration. Easily configurable Web client also supported.
                    No CR/LF issues. Scripts are all portable as well.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">
                    Very good - various flavours of Unix,
                    Windows (only NT family for the server), VMS, and 
                    possibly other systems.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Windows only: starting with Win95.</td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    Very good. Supports many UNIXes, Mac OS X, and Windows,
                    and is written in a portable language.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">
                  The client works on most UNIXes, but not on native MS-Windows. The cygwin build
                  seems to be workable, though.
              </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Excellent. Clients and servers work on any Java 1.5-compatible
                  platform. (Windows, Linux and Mac OS X )
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    Excellent. Runs on all platforms supported by
                    Python.  Repositories are portable across CPU
                    architectures and endian conventions.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    Excellent. Executable is portable across all UNIXes and
                    Win32.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    Good. Portable across all UNIX systems.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Excellent. Runs on UNIX, Mac OS, BeOS and Windows.
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Excellent. Client and Server run on Windows, Linux,
                    Solaris and other UNIXes. The client also runs on Mac
                    OS X.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Good. The server runs on Windows only.
                 Clients can work on any platform that SWT (Standard Widget Toolkit) supports,
                  including Windows, Linux, Mac, Solaris, AIX, HP-UX, SCO Unix, FreeBSD and so on.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    Excellent. Clients and Servers work on UNIX, 
                    Windows and Mac OS X.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                    Excellent. Clients and servers work on any Java
                    1.4-compatible platform. There is official support
                    for Windows, Linux and OS/2.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">
                    Good. Clients requires subversion and its perl bindings.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">
                The Server and Client needs Windows. A thirdparty company,
                Teamprise, has developed a client for Eclipse, which means 
                Linux, Mac and other UNIXes support. The Project SvnBridge 
                allows access using SVN clients but needs to run on Windows.
              </td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Good.  It should be portable to any UNIX system.
                    Currently it runs on Digital/Compaq/HP Tru64 UNIX
                    and Linux on several different CPU architectures.
                    Ports to Solaris and FreeBSD are planned but
                    haven't begun yet.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    The Microsoft Product is Windows only. 
                    <a href="http://www.mainsoft.com/">MainSoft</a>
                    ships a version of it for some UNIX platforms.
                </td>
</tr>
</table>
<h2 id="user_interaces">User Interfaces</h2>
<h3 id="web_interface">Web Interface</h3>
<p class="expl">
                Does the system have a WWW-based interface that can be
                used to browse the tree and the various revisions of the
                files, perform arbitrary diffs, etc?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">Yes. 
                    <a href="http://www.freebsd.org/projects/cvsweb.html">CVSweb</a>,
                    <a href="http://www.viewvc.org/">ViewVC</a>,
                    <a href="http://www.horde.org/chora/">Chora</a>,
                    and <a href="http://wwcvs.republika.pl/">wwCVS</a>.
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    There's <a href="http://arch.bluegate.org/viewarch.html">ViewARCH</a>, and 
                    <a href="http://migo.sixbit.org/software/archzoom/">ArchZoom</a>
                    which are 
                    works in progress.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    Yes, several:
                    <a href="http://www.lag.net/loggerhead/">Loggerhead</a>,
                    <a href="http://goffredo-baroncelli.homelinux.net/bazaar/">Webserve</a>,
                    <a href="http://mccormick.cx/dev/bzrweb/index.py/log/bzrweb/head">Bzrweb</a>,
                    and
                    <a href="http://bazaar-vcs.org/TracBzr">Trac</a>.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">Yes. Its own built-in web-interface.</td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Yes. Web views are supported.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Yes.  Can be configured to restrict which operations
                    are allowed by which users, so that customers may access their
                    requests without seeing development team data.
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">Possibly.</td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Since this functionality is always 
                    available locally, there is no need for web interface.
                </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    <a href="http://abridgegame.org/cgi-bin/darcs.cgi/darcs/">darcs.cgi</a>
                    is included in the distribution.
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">
                    Yes.  Gitweb is included in distribution.
                </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  Yes, without diff features but with a better awareness support.
                  (allow to know at any time on each version each one is working on) 
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">Yes.  The web interface is a bundled component.</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">Yes, P4Web.</td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">Yes.</td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Currently not.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">Yes. 
                    <a href="http://www.viewvc.org/">ViewVC</a>,
                    <a href="http://freshmeat.net/projects/svnweb/">SVN::Web</a>,
                    <a href="http://websvn.tigris.org/">WebSVN</a>, 
                    <a href="http://viewsvn.berlios.de/">ViewSVN</a>,
                    <a href="http://www.outoforder.cc/projects/apache/mod_svn_view/">mod_svn_view</a>, 
                    <a href="http://www.horde.org/chora/">Chora</a>,
                    <a href="http://www.edgewall.com/trac/">Trac</a>,
                    <a href="http://web-cpan.berlios.de/modules/SVN-RaWeb-Light/">SVN::RaWeb::Light</a>,
                    <a href="http://www.polarion.org/svnbrowser.php">SVN
                        Browser</a>,
                    <a href="http://insurrection.tigris.org/">Insurrection</a>
                    and <a href="http://www.osdevel.org/projects/show/16?lang=en">perl_svn</a>.
                    Aside
                    from that, the Subversion Apache service provides a
                    rudimentary web-interface.
                    </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">No.</td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Yes. Same as Subversion.</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">Web Access is available as download for free.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    Yes: <a href="http://www.scooter.cx/vestaweb/">Vestaweb</a>.
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    It is possible to code one using the API, but no official
                    or third-party one exists.
                </td>
</tr>
</table>
<h3 id="availability_of_guis">Availability of Graphical User-Interfaces.</h3>
<p class="expl">
                What is the availability of graphical user-interfaces for
                the system? How many GUI clients are present for it?
            </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">Very good. There are many available GUIs:
                    WinCVS, Cervisia (for KDE),
                    TortoiseCVS (Windows Explorer plug-in).
                </td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">
                    A single, comprehensive,
                    java-based GUI is provided.  The GUI has the same 
                    look-and-feel on all platforms.
                </td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                    There is tkaegis.
                </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">
                    There are
                    <a href="http://www.ibe.miee.ru/tlator/">tlator</a>,
                    <a href="http://www.hpl.hp.com/personal/Yasushi_Saito/octopy/">Octopy</a>,
                    and <a href="http://www.nongnu.org/archway/">ArchWay</a>
                    and possibly others under development.
                </td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">
                    There are several graphical frontends in
                    development,
                    see <a href="http://bazaar-vcs.org/BzrPlugins">the Bazaar Plugins page</a>
                    and <a href="http://bazaar-vcs.org/3rdPartyTools">the Third-party Tools page</a>.
                    Notable
                    are <a href="http://bazaar-vcs.org/QBzr">QBzr
                    (Qt)</a> and 
                    <a href="http://bazaar-vcs.org/bzr-gtk">bzr-gtk (GTK+)</a>, which
                    can be considered beta quality.  Work is also
                    being done on integrating Bazaar with Windows
                    Explorer, Eclipse, Nautilus, and Meld.
                </td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                    Good. BitKeeper ships with several
                    GUIs for performing common tasks. I'm not aware
                    of any third-part GUIs.
                </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
                  Supplied for both Windows and UNIX. GUI tools are
                  typically not as solid as the command-line tools
                  though.
                </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc">
                    Excellent.  Windows and Unix/Linux GUI as well
                    as web GUI.  Extensively configurable via simple menu files,
                    browser files, etc.  Can customize the set of to-do lists by
                    user/role, same for menus, pop-up menus, default visible tabbed
                    reports, etc.  GUI also used for all admin and for process
                    and data schema customization.  Also plug-in for Visual Studio,
                    Eclipse, etc. and File Browser (Windows).
                </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">
                    A couple of GUIs.  A motif-based one
                    (even on Windows) allows most functionality but is clunky.
                    A nicer Java one allows developer work but not much 
                    administrative stuff. Has an SCCI plug-in, though it 
                    doesn't handle network problems well.
                </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">The system is GUI-based by design.</td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">
                    None to speak of.  (There is a modest graphical
                    interface to a few commands in the distribution, but it
                    is not being developed currently.)
                </td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">
                    Gitk is included in distribution.  Qgit and Git-gui tools are also available.
                </td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">
                  One written in Java/SWING and available on any OS that
                  is automatically launched from the repository web page and 
                  another one which is an Eclipse plugin.
                </td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">
                    History viewing available with hgit extension;
                    check-in extension (hgct) makes committing easier.
                    Some third-party IDEs and GUI tools (e.g. eric3,
                    meld) have integrated Mercurial support.
                </td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">
                    No GUIs are available.
                </td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                    No GUIs are available.
                </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                    Yes, P4Win and others based on the available libp4 
                    library. 
                </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                    Cross-platform GUI for Windows, Linux, Mac OS X
                    and other UNIXes.
                </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">The system is GUI-based by design.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                    Very good. There are many available
                    GUIs: RapidSVN (cross-platform),
                    TortoiseSVN (Windows Explorer plug-in), Jsvn (Java), etc.
                    Most of them are still under development.
                </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                    A GUI is integrated.
                </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">
                    No GUIs are available.
                </td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">TFS client integrates into Visual Studio.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                    No GUIs are available, but the repository has a
                    C++ API, and it is not hard to write one.  (At
                    least three different project-specific ones have
                    been written by users at Compaq and Intel.)
                </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                    Standalone GUI comes with it, plus SCCI plug-in for 
                    MS Visual Developer Studio. There is an Eclipse 
                    plug-in.
                </td>
</tr>
</table>
<h2 id="license">License</h2>
<p class="expl">
            What are the licensing terms for the software? 
        </p>
<table class="compare">
<tr>
<td class="sys">CVS</td>
<td class="desc">GNU GPL (open source)</td>
</tr>
<tr>
<td class="sys">AccuRev</td>
<td class="desc">Proprietary, named-user licensing.</td>
</tr>
<tr>
<td class="sys">Aegis</td>
<td class="desc">
                GNU GPL (open source)
            </td>
</tr>
<tr>
<td class="sys">Arch</td>
<td class="desc">GNU GPL (open source)</td>
</tr>
<tr>
<td class="sys">Bazaar</td>
<td class="desc">GNU GPL (open source)</td>
</tr>
<tr>
<td class="sys">BitKeeper</td>
<td class="desc">
                Proprietary, binary only license. Pay per use license,
                with an option for a costless license for developers of
                open-source software. Used to have a gratis, downloadable 
                license, which was intended for the develpoment of open
                source software. It had <a href="bk-license.html">a 
                    problematic license</a>,
                and was discontinued starting at April 2005.
            </td>
</tr>
<tr>
<td class="sys">ClearCase</td>
<td class="desc">
              Proprietary, with floating license supported. License
              server contacted for each clearcase operation, which
              obtains a license to be used for the next 30-60
              mins. Prices are several $k per license plus yearly
              maintenance fee. Typically 1-3 users per license
              required, depending on activity. Multisite requires
              additional licensing.
            </td>
</tr>
<tr>
<td class="sys">CM+</td>
<td class="desc"> Network licenses and user licenses. No minimum
                checkout time, and automatic license checkin on idle. License
                server included in product. Professional and Enterprise editions.
                Enterprise includes customizations, additional applications, and
                full multiple site capability.  One Server license per site. Total
                license cost per user typically less than $1000 + 18% annual mtce.
            </td>
</tr>
<tr>
<td class="sys">CMSynergy</td>
<td class="desc">
                Prices negotiable with salesman.
                Server is typically roughly 20,000 British Pounds.  
                Clients are 4,000 British Pounds.  Per-year costs of 18% 
                of original.
            </td>
</tr>
<tr>
<td class="sys">Co-Op</td>
<td class="desc">Proprietary, short text key. 30-day 
                full-featured trial. Free to "observers" 
                (members who don't make changes).
                $159 per workstation.
            </td>
</tr>
<tr>
<td class="sys">Darcs</td>
<td class="desc">GNU GPL (open source)</td>
</tr>
<tr>
<td class="sys">Git</td>
<td class="desc">GNU GPL v2 (open source).</td>
</tr>
<tr>
<td class="sys">LibreSource Synchronizer</td>
<td class="desc">QPL - The Qt Public License (OpenSource)</td>
</tr>
<tr>
<td class="sys">Mercurial</td>
<td class="desc">GNU GPL (open source)</td>
</tr>
<tr>
<td class="sys">Monotone</td>
<td class="desc">GNU GPL (open source)</td>
</tr>
<tr>
<td class="sys">OpenCM</td>
<td class="desc">
                GNU GPL (open source), but moving soon to
                BSD or CPL (also open source).
            </td>
</tr>
<tr>
<td class="sys">Perforce</td>
<td class="desc">
                A proprietary, binary only, commercial license.
                <a href="http://perforce.com/perforce/price.html">Price
                    starting at $800 per seat for the first year</a> and then
                a $160 for continuing support for the subsequent years. The
                latter payment is optional and required only for support,
                as the product can be used without it. Free for 
                Open Source projects (no support in this case).
            </td>
</tr>
<tr>
<td class="sys">PureCM</td>
<td class="desc">
                A proprietary, binary only, commercial license. 
                <a href="http://www.purecm.com/purchase">Price 
                    starting at $1000 for 5 users</a>
            </td>
</tr>
<tr>
<td class="sys">SourceAnywhere</td>
<td class="desc">Proprietary, named-user licensing.</td>
</tr>
<tr>
<td class="sys">Subversion</td>
<td class="desc">
                Apache/BSD-style license. (open-source)
            </td>
</tr>
<tr>
<td class="sys">Superversion</td>
<td class="desc">
                GNU GPL (open-source)
            </td>
</tr>
<tr>
<td class="sys">svk</td>
<td class="desc">Perl License. (open source)</td>
</tr>
<tr>
<td class="sys">Team Foundation Server</td>
<td class="desc">Commercial license.</td>
</tr>
<tr>
<td class="sys">Vesta</td>
<td class="desc">
                GNU LGPL (open source)
            </td>
</tr>
<tr>
<td class="sys">Visual SourceSafe</td>
<td class="desc">
                VSS Ships with MSDN, and can also be purchased
                standalone or with other tools.
            </td>
</tr>
</table>
</body>
</html>