Open Source Unix Shell Version Control Software - Page 3

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.

This tool is designed to help you use git more efficiently. It's lightweight and easy to use. Fig adds apps, shortcuts, and autocomplete to your existing terminal. Options can be set via environment variables. They have to be exported in order to be recognized by forgit. You can use forgit as a subcommand of git by making git-forgit available in $PATH. Forgit will use the default configured pager from git (core.pager, pager.show, pager.diff) but can be altered with several environment variables. You can add default fzf options for forgit, including keybinds, layout, etc. (No need to repeat the options already defined.

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

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.

A bash script to watch a file or folder and commit changes to a git repo. Some programs auto-write their config files, without waiting for you to click an 'Apply' button; or even if there is such a button, most programs offer you no way of going back to an earlier version of your settings. If you commit your config file(s) to a git repo, you can track changes and go back to older versions. This script makes it convenient, to have all changes recorded automatically. If you use an editor that does not have built-in git support (or maybe if you don't like the git support it has), you can use gitwatch to automatically commit your files when you save them, or combine it with the editor's auto-save feature to fully automatically and regularly track your changes. If you have any other uses, or can think of ones, please let us know, and we can add them to this list! gitwatch can be installed from source by simply cloning the repository and putting the shell script into your $PATH.

In Unix, configuration files are king. Tailoring tools to suit your needs through configuration can be empowering. An immense number of hours is spent on getting these adjustments just right, but once you leave the confines of your own computer, these local optimizations are left behind. By the power of git, homeshick enables you to bring the symphony of settings you have poured your heart into with you to remote computers. With it you can begin to focus even more energy on bettering your work environment since the benefits are reaped on whichever machine you are using. However bare bones these machines are, provided that at least Bash 3 and Git 1.5 are available you can use homeshick. homeshick can handle multiple dotfile repositories. This means that you can install larger frameworks like oh-my-zsh or a multitude of emacs or vim plugins alongside your own customizations without clutter.

A flatfile-based metadata repository and integration with common build tools (make, ant, others). A code generation framework is included and is useful to conditionally generate code objects based on the deployment environment. Metadata+deploy = :)

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.

nvm.fish is a Node.js version manager tailored specifically for the Fish shell, allowing users to install and switch between multiple Node.js versions seamlessly.

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.

A minimal, lightweight, informative zsh prompt theme. Clone the typewritten repository somewhere you can easily link. I recommend creating a .zsh directory at root. typewritten is customizable in many ways. Prompt customization, everything to do with how and where the info is displayed. Prompt color customization set a custom color for any of the prompt sections.

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