Chora is built upon the Horde Application Framework and provides a read-only browser interface to any number of version control repositories. Advanced features include a visual branch view of the repository's history, pretty-printed output, annotation, patchsets and basic statistics.
FishEye opens your source code repository to help you understand your code and keep tabs on the people who write it. It lets you view user activity, track code changes, and search and navigate through your repository from any Web browser. Nearly everything in your repository has its own URL, down to every single line of code for every revision. Files, branches, repositories, projects, and even people have their own activity stream. FishEye provides easy navigation, powerful search, historical reporting, configurable file annotation and diff views, changeset analysis, RSS feeds, and integration with JIRA, Crucible, Bamboo, Eclipse, and IntelliJ IDEA. FishEye works with Subversion, CVS, Perforce, Git or Mercurial.
Submin provides a Web-based admin interface to your Subversion and Git repositories. Its features include user/group management, path permission management, the ability to create svn repositories and managing commit email messages. For Subversion, authentication is done with htpasswd/svn authz, so it can use the same login information as apache2/svn (and trac). For Git, ssh is used, and the login information is synched whenever a change is made. The Web interface can also work with NGINX/uWSGI, but the Subversion part only works with Apache.
Git# is a C# implementation of the Git version control system for the .NET platform. It is meant to be fully compatible to the original Git implementation in C for Linux. It can be used as a stand-alone command line application (potentially replacing msysGit on Windows) or as a library for applications such as GUI frontends or plugins for IDEs.
CVS, GIT, and Mercurial as well as other well-known version control systems cannot version directories. In other words, you cannot add empty directories. A "workaround" for this issue is to use placeholder files that are placed into empty directories. These placeholder files can then be committed into the repository and will make sure that, upon checkout, the directory tree is entirely reconstructed. The problem with using placeholder files is that you need to create them, and need to delete them if they are not necessary anymore (because sub-directories or real files were added). With big source trees, managing these placeholder files can be cumbersome and error prone. MarkEmptyDirs can manage the creation/deletion of such placeholder files automatically. It creates placeholder files in all empty "leaf" directories. If later on new files or directories are put into such directories, the placeholder files are not necessary anymore, and are removed automatically.
TurnKey Revision Control Appliance is an integrated revision control server combining the best open source version control systems: Subversion, Git, Bazaar, and Mercurial. A Web interface is included for each system, making it easy to browse through the code base, compare revisions, and manage repositories for multiple projects. No configuration is required and security patches are automatically installed. A Web management interface, configuration console, and AJAX Web shell are provided. To minimize footprint the appliance is built from the ground up with the minimum required components. It runs everywhere thanks to multiple build formats, including an installable live CD, a VMDK with OVF support, and an Amazon EC2 AMI.