Open Source Unix Shell Version Control Software - Page 3

SvnCrawler is a tool for analysis of Subversion (SVN) repositories. The project includes different plug-ins for generating csv reports, rss feeds and more. Creating a new plug-in takes only a few bash lines. More info: http://svncrawler.sourceforge.net

SAVT is a set of shell scripts which allow you to put config files under version control using Subversion with support for metadata versioning (permissions, ownership) and share them with certain host types.

ucmi (Unified Change Management Interface) provides an abstraction layer, in the style of the Unified Change Management model, to version control tools and defect tracking systems.

XEmacs is a highly customizable text editor and application development system. Its emphasis is on modern graphical user interface support and an open software development model.

aepro is a dependency maintenance tool for progres4gl. It is intended to be used in conjuction with aegis (aegis.sourceforge.net), a source code configuration tool. It (re)compiles progres4GL programs whose sourcecode has changed.

Braincracks acts like a continuous snapshoting filesystem / versioning filesystem. It monitors folders for files changes (each X seconds) and saves a copy of files when they change. It is made of 3 Bourne Shell scripts (1 bin, 1 daemon, 1 service).

CKBDT -- Backup and diff tools. Easy and straightforward source code management. Three commands : dtag (select target directory), dsto (backup target directory), ddif (compare target directory with latest backup).

cvsbackup is a perl-based tool for backuping your files and sending diffs via e-mail. package also includes scheduler (optional) which helps you monitor more than 1-2 servers (helps to prevent high loads on config repository).

CvsKnit is a toolset to automate knitting up CVS repositories from existing source packages. This is a sub-project of minix-up project (SF.jp).

cvsq (CVS queued) is a tool that enables developers with a dial-up connection to work comfortably with CVS. It accepts same arguments as CVS but instead of directly processing them, cvsq stores all requests in a queue and handles them later.

gc-utils is a small set of scripts that let you import and update CVS repositories into git very easy and let you export patches back into a CVS working copy.

git core, the distributed source control system

Type git open to open the repo website (GitHub, GitLab, Bitbucket) in your browser. git open works with these hosted repo providers, git open --issue currently only works with GitHub, Visual Studio Team Services and Team Foundation Server. The preferred way of installation is to simply add the git-open script somewhere into your path (e.g. add the directory to your PATH environment or copy git-open into an existing included path like /usr/local/bin). Antigen will handle cloning the plugin for you automatically the next time you start zsh, and periodically checking for updates to the git repository. You can also add the plugin to a running zsh with antigen bundle paulirish/git-open for testing before adding it to your .zshrc. Add zgen load paulirish/git-open to your .zshrc file in the same function you're doing your other zgen load calls in. ZGen will take care of cloning the repository the next time you run zgen save, and will also periodically check for updates to the git repository.

An interactive way to peruse your git history from the terminal. git-recall is a simple tool that allows you to easily go through your commits and check what you or other contributors in your team did. It doesn't aim to be a replacement for the git log command, but just to be a convenient way to recall what you've done from your terminal. You can install it by simply copying the git-recall script into any existing path (e.g. /usr/local/bin) or create your own directory and add it to the PATH variable. Once the commits are displayed, you can use either the arrow keys or j/k to switch between commits, press TAB or e to expand/reduce the commit's diff or q to quit.

There’s a well-known issue with deploying and configuring software on servers: generally, you have to store your private data (such as database passwords, application secret-keys, OAuth secret keys, etc) outside of the git repository. If you do choose to store these secrets unencrypted in your git repo, even if the repository is private, it is a security risk to copy the secrets everywhere you check out your repo. These files are not version controlled. Filenames, locations, and passwords change from time to time, or new information appears, and other information is removed. When secrets are stored separately from your repo, you can not tell for sure which version of the configuration file was used with each commit or deploy. When building the automated deployment system there will be one extra step: download and place these secret-configuration files where they need to be. This also means you have to maintain extra secure servers where all your secrets are stored.

minirepo (abreviated to mr) is designed to handle small to middle sized repositories with rcs. It supports version bumping and snapshoting, which is simmilar to a git or fossil commit hash It keeps track of files checked into the repo via a MANIFEST file The main configuration is located inside the MR/ directory for each subdirectory initialized. Its priamry purpose is to track files with rcs related commands. This is to make it easier to deal with a lot of files tracked by rcs and also to offer some extra functionality like snapshots and automatic versioning.

PMS is a small tool aimed at maintaining local branches independent of current VCS (Version Control System) used. Currently PMS supports the following VCS-es: CVS, SVN, GIT.

rcss - rcs simplified. RCS is revision control. While the newer revision controls like git have taken the world by storm, I find as a systems administrator that I don't need all the features of git, I need some thing simple and that stays on my server and is simple and easy to use. RCS fit the bill for me for revision control. RCS didn't make it easy to do things like compare, revert. So I wrote rcss, to make working with rcs MUCH simpler, at least for myself. I hope you find it as useful as I have.

srtools is a set of simple remote tools. the main two to mention: simple rdist distributes files or commands across hosts. srdist(1) understands rcs(1) files and host based files. there are several other tools see README. rcs tools has a few things , like "late-checkins" to check for files that one forgot to check in an dorev to force check in / do easy check in (avoiding complicated options). host based files is a way to allow hosts to distribute all files without clobbering host specific files. and with that ... srtools(1) makes partially synchronizng hosts easy. Also can be a far easier way to do incremental or nightly backups. Also an easy way to have multiple hosts interact. README is visible on file download page EXAMPLE: $rcssrdist file (file was broadcased to default hosts list that are up. if a rcs pair existed it was taken care of. existence of directory on other hosts was checked (common mistakes checked)

This is an add-on to stow. If the "make install" didn't work with DESTDIR argument(or use another installer), stow-jail would close the installer command to the sandbox(unionfs+chroot),in this way all go to the "/stow/package_name" directory.

A set of scripts named "svnexport" is intended to update the Web site from the Subversion repository by using "svn export [options]" command. You can work through a Web interface or from the command line.

A plug-in element for CruiseControl to detect tag related modifications in a source code repository (CVS).

A script to configure transparent encryption of sensitive files stored in a Git repository. Files that you choose will be automatically encrypted when you commit them, and automatically decrypted when you check them out. The process will degrade gracefully, so even people without your encryption password can safely commit changes to the repository's non-encrypted files. transcrypt protects your data when it's pushed to remotes that you may not directly control (e.g., GitHub, Dropbox clones, etc.), while still allowing you to work normally on your local working copy. You can conveniently store things like passwords and private keys within your repository and not have to share them with your entire team or complicate your workflow. transcrypt is in the same vein as existing projects like git-crypt and git-encrypt, which follow Git's documentation regarding the use of clean/smudge filters for encryption.

This script make a copy of a file, in the directory ".vers" with a timestamp on the end.

full cvs web based client using original cvs backend ofcourse:) this cvs web client is designed to be easy to use, and powerful cvs client