Search Results for "cvs concurrent version control"

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...

It's a web application which provides a unify solution to stat. CVS/SVN repository modules code change information and generate html reports. User can browse line of change, file of change, code diff, check-in comment and so on, it can stat. more repository modules one time. After repository modules configured, stat. is simple like a search.

It's a web application which provides a unify solution to stat. CVS/SVN repository modules code change information and generate html reports. User can browse line of change, file of change, code diff, check-in comment and so on, it can stat. more repository modules one time. After repository modules configured, stat. is simple like a search. It's the mirror project of CodeChangeViewer: http://sourceforge.net/projects/ccv/.

QB (Quellcode Bahn) is a software that manage the operations on the source of the programs you develop, with a versioned repository. QB manage the deploy of your program, taking it from the repository and putting it wherever you want with test phase.

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

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.

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.

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).

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.

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).

JViewCVS is a Java-based(JSP) web application for viewing a CVS repository. The goal of this project is to create the same functionality as viewcvs, but written in JSP.

The enclosed Python scripts differ from most other commit notification solutions in that they coalesce all of the commit operations from a single \\\"cvs commit\\\" command into a single email. Most other solutions will send one email per directory.

CVSGI (Concurrent Versions System Graphical Interface) is a Java based GUI application which works with the CVS archiving system. ‘CVSGI’ GUI acts as an interface between the user and the CVS system.

Provide secure and stable OS, based on highly modified Linux Kernel, own package system, like "BSD Ports". Compatible with x86, Power PC. Easy to use of any level users. Complete Documentantion in many languages. 99% compatible with Windows.

The SoftChange project will create software to summarize and analyze software changes in CVS repositories and defect tracking systems (Bugzilla/GNATS).

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

CVS tools - set of utilities for users, project/build managers and system administrators. The tools use platform independent languages like bash, Perl, Python or Java. Platform support Win32/Cygwin and Linux based file systems. PROJECT MOVED. See Github user jaalto.

This project provides a coherent package of utilities that simplify the task of tagging, customising and packaging releases of code taken from CVS, together with documentation about release conventions and suggested practices.

The aim of this project is to make it easier to keep the source code updated with the server on projects that use CVS. Keeping up to date source files on SourceForge.com projects will be automated.