Free version control software for linux

VolumeControl is a audio mixer for GNU/Linux.
Volume Control project requires OSS or ALSA with OSS /dev/mixer compatibility (for now) from the Linux kernel.
The GTK interface provides ease of use in adjusting volume levels.
Features to be added before version 1.0:
- add full ALSA support
- add volume themes
- additional testing
Enhancements:
- Command line arguments have been added.
- The GUI can be bypassed by using command line arguments.
- This makes volumecontrol useful for scripts, or for users who prefer adjusting levels without a GUI.

The Bazaar Revision Control System is a changeset-oriented revision control system based on Arch that makes it possible to retain previous changes to projects and coordinate development with other developers.
Its goal is to speed development of an upwards- compatible version of Arch.
Main features:
- All the transparent and robust storage features of GNU Arch.
- seamless upgrade path to [WWW] bazaar-ng
- direct support for URLs - one command can checkout or merge from remote locations.
- integrated GPG support - zero setup for most signed archive situations
- faster - checkout, most local operations, commits
- svn-like diff, switch, import, export, log commands
- Explicit tracking of conflicts, preventing accidental commits of files with conflicts
- single merge command that allows merging between arbitrary branches.
- Daily builds of the latest code (Downloads).
- fully compatible with tla - drop in and start using
- supports debian version numbers in branch names
- annotate support
- internationalised via gettext and [WWW] Rosetta.
- Python bindings.
Enhancements:
- More Solaris fixes.
- SSL support and ~/.authinfo support.
- Many UI tweaks.
- A number of bugfixes.

Master Combat Control Program is an improved clone of the "Shadowrun-Assistent" program (as found on shadowrun.de).
Its main goals are better usability, minor feature improvements, and i18n. It constists of a character editor, an initiative manager, and a dice roller.
Enhancements:
- Due to popular demand, the directory where the configuration files are put is now configurable via the "-config" option.
- When first running the program it complained about missing files, which are created on shutdown, so this was changed.
- added parsing of command line parameter "-config";
- all error messages internationalized;
- added "readme.txt"

Device Control Device is a platform independent remote telescope and device control program compatible with the INDI standard (see http://indi.sourceforge.net/).

This program is a client (a user interface) and provides functions to control devices connected to a remote system that is running an INDI server.

The features and the structure of the GUI are similar to the Kstars INDI client. The only advantages are support for Windows and lower resource requirements.

Backup project adds instant version control to any file on a Unix system.

Do you hate *.bak and *.20050101 and *.cjn (your initials here) and *.do.not.touch files as much as I do? They litter your filesystem any time someone (and were all guilty of it) needs to back-up a file theyre working on.

But who ever comes back and cleans the mess up? At what point is an old backed-up file no longer needed? And what about when you need that backup file only to discover that its missing, or you didnt capture one because you didnt want to add clutter? Backup is my answer to all that. It adds instantly available, reliable version control to every file in the filesystem.

Backup is a lightweight interface to the Subversion svn_fs library. It uses the powerful version control software as a backend to a simple and minimalistic (though effective) user interface. It is designed for use on Linux/Unix (including OS X) systems as a method of archiving configuration files that change semi-frequently, but do not necessarily warrent their own version control mechanism or repository. Things like "/etc/hosts" or "httpd.conf".

It can create a backup of any file without having to import it first, without worrying about setting up new repositories, and (because it speaks directly to the FS layer) without littering hidden ".svn" (or even worse, visable "CVS") directories all over the place. It does this by using a single global "archive," which contains a filesystem that mirrors your root as you add to it. You can view the archive and restore files, do diffs, and move things around as necessary. For more complex administration, the archive is a standard Subversion file system which can be administrated with any compatable client (including the svn command line tools).

The current version is knocked together in Perl. Its alpha, but it is pretty functional... at least for a proof of concept. Eventually I plan to re-write it in C... but we all know about "the best laid plans." In the mean while, the Perl version does work... mostly. The only real trick is that you need to compile and install the Subversion bindings for it Perl. There are some other modules you may need as well, but theyre all fairly standard.

Usage:

You probably shouldnt if you youre doing mission-critical work. Its still alpha code after-all. But if you do decide to give it a spin, dont blame me for any breakage (the only thing that should damage existing files is the combination of -r and -o, which will overwrite during a restore).

Cervisia is a GUI frontend for the version control system CVS. Cervisia project has features like a blame-annotated view, tagging and branching, a changelog editor coupled with the commit dialog and view of the log messages in a tree and list form.
Cervisia is shipped with the KDESDK package.
Main features:
- Updating or retrieving the status of a working directory or single files. Files are displayed in different colors depending on their status, and the shown files can be filtered according to their status
- Common operations like adding, removing and commiting files.
- Advanced operations like adding and removing watches, editing and unediting files, locking and unlocking.
- Checking out and importing modules.
- Graphical diff against the repository and between different revisions.
- Blame-annotated view of a file.
- View of the log messages in tree and list form.
- Resolving of conflicts in a file.
- Tagging and branching.
- Updating to a tag, branch or date.
- A Changelog editor coupled with the commit dialog.

Ops Control Panel is a frontend for MRTG.

Unlike many other frontends, it does not have any requirements beyond those of MRTG, although it can support PHP-enabled Web servers instead of just running as a Perl CGI script.

Ops Control Panel project provides overviews of MRTG-based monitoring pages in a variety of formats.

Anyone who has spent enough time in Linux probably believes that you can never have enough control.

LPQ Control PHP script is a tool that parses the output of the lpq command and provides a web interface that allows you to remove print jobs from a printer.

You need to make sure that Apache can execute the lprm command. For a
default Apache installation, you will need to add the following line to
your /etc/sudoers file:

apache ALL=(root) NOPASSWD:/usr/bin/lprm

This allows the PHP program to remove *ANY* specified print job.