
	Where results make sense

Topic: Revision Control System

Related Topics

DPX

Real number

SPP

Roy Campbell (poet)

James Henry Pullen

Nahum

Pavel Yablochkov

Looe

Wharf

John Holmes

Waltham Watch Company

Arts and crafts

Folly Beach, South Carolina

New Tokyo International Airport

From the Screen to Your Stereo

In the News (Fri 17 Feb 12)

EXECUTIVE POWER

Iran

ANALYSIS

Pakistan

Family compact

	Revision control - Wikipedia, the free encyclopedia
		Revision control (also known as version control) is the management of multiple revisions of the same unit of information.
		Traditionally, revision control systems have used a centralized model, where all the revision control functions are performed on a shared server.
		A few years ago, systems like TeamWare, BitKeeper, and GNU arch began using a distributed model, where each developer works directly with their own local repository, and changes are shared between repositories as a separate step.
	en.wikipedia.org /wiki/Revision_control (1375 words)

	Revision control at opensource encyclopedia (Site not responding. Last check: 2007-10-08)
		Revision control is an aspect of documentation control wherein changes to documents are identified by incrementing an associated number or letter code, termed the "revision level", or simply "revision".
		In computer software engineering, revision control is any practice which tracks and provides controls over changes to a project's source code.
		Most use a system whereby only the differences between successive versions of files are retained, thus allowing the efficient storage of many, many different versions of files.
	www.wiki.tatet.com /Version_control_system.html (669 words)

	Revision Control System manpage (Site not responding. Last check: 2007-10-08)
		A range of the form rev1:rev2 means revisions rev1 to rev2 on the same branch, :rev means from the beginning of the branch containing rev up to and including rev, and rev: means from revision rev to the end of the branch containing rev. None of the outdated revisions can have branches or locks.
		The RCS pathname and the revisions outdated are written to the diagnostic output.
		The separator for revision ranges in the -o option used to be - instead of :, but this leads to confusion when symbolic names contain -.
	www.cs.buffalo.edu /~merupp/manPages/RCSmanpage.html (1391 words)

	Csite Software - Revision Control System for RiscOS
		Revision control is an automated system for programmers to keep track of the changes they make in their source files.
		I chose RCS, the Revision Control System, because it was available from GNU and is pleasant for the user to work with.
		A list can be produced of all revisions, showing what date and time they were checked in and by whom, and showing the comment that was entered for each revision.
	www.xs4all.nl /~erikgrnh/riscos/rcsinfo (807 words)

	Linux Development Tools: Tools - Revision Control (Site not responding. Last check: 2007-10-08)
		CVS is a version control system, which allows you to keep old versions of files (usually source code), keep a log of who, when, and why changes occurred, etc., like RCS or SCCS.
		It has two particularly distinctive features which differ from other revision control systems: each copy of the source is a fully functional branch, and underlying it is a consistent and powerful theory of patches (the latter being darcs' most important feature).
		PRCS (Project Revision Control System) is the front end to a set of tools that provide a way to deal with sets of files and directories as an entity, preserving coherent versions of the entire set.
	www.hotfeet.ch /~gemi/LDT/tools_rev.html (1950 words)

	np237: On distributed revision control systems (Site not responding. Last check: 2007-10-08)
		Distributed revision control is a useful tool, but no one's yet demonstrated how to use it sanely without keeping a centralized development process, negating most of its supposed benefits (really, all you keep is offline operation).
		One technical way to skirt around this is to use a centralised revision control system (either nominate one central branch which everyone can merge to as the branch, or use CVS/SVN/whatever), but eventually the lack of any visible leader will come to bite you on the butt.
		You provide an extremely weak argument against "distributed" revision control (how exactly are they not distributed); having to rely on slanderous generalizations such as "shit" or "complete mess".
	np237.livejournal.com /5457.html (1653 words)

	epowiki: Revision Control System (Site not responding. Last check: 2007-10-08)
		Revision control systems facilitate the sharing of files among multiple users.
		version control - multiple revisions of the same file are stored and older revisions are always accessible.
		bugs and system integration - requests can be tracked from entry to fix; this capability is known as defect tracking or change management.
	www.possibility.com /epowiki/Wiki.jsp?page=RevisionControlSystem (195 words)

	Ch 23 -- Introduction to Revision Control (Site not responding. Last check: 2007-10-08)
		Demonstrate essential revision control concepts, such as creating revisions, checking changes in and out of the system, how file changes are logically organized and how the systems can be used to easily move between file revisions.
		System administrators have to manage a variety of configuration changes, such as adding new users to systems and adding new systems to networks, without interfering with day-to-day operations.
		Note that even though revision 1.7 is the descendant of 1.6, it doesn't contain the changes Arthur made, since the revision control system simply replaced 1.6 with 1.7.
	docs.rinet.ru /UNIXi/ch23.htm (3760 words)

	Personal info for jblack
		In a revision control system the merging of specific patches from two distinct, but related, tree is very simple.
		Locking people out of revision control is not the cure to ensure the cohesiveness of a project.
		Whether or not one agrees with Raymond's paper, one thing is certainly true: A non-distributed revision control system is the establishment of a cathedral type system.
	www.advogato.org /person/jblack (1521 words)

	An Idea for a Revision Control System (Site not responding. Last check: 2007-10-08)
		With this system, you would select the revisions you want to apply, and can specify that one is more important than another.
		In order for this to work, the revision packaging system has to be capable of handling changes to any type of file, changes to directory structure, and logs of activities.
		One major goal would be to keep the system language and platform neutral with very minimal requirements for installing a client or mediator (or, even allow operating without a mediator).
	www.zedshaw.com /blog/programming/an_rcs_idea.html (1423 words)

	GNU arch -- a revision control system - Summary [Savannah]
		GNU arch is a revision control system, similar in purpose to tools such as CVS, SCCS, and Subversion.
		That means, for example, that I don't need to give you write access or special permission to create revision controlled changes to software I publish: you can just create your own archive for that, and treat it as an extension of mine.
		Advanced users of revision control often make very heavy use of branching and merging features -- the design of arch attempts to provide the best possible support for that style of work.
	savannah.gnu.org /projects/gnu-arch (641 words)

	freshmeat.net: Project details for arch revision control system
		They have been replaced by spares revision libraries (these are the recommendations, in fact they are there but I'm sure they'll dissappear in a couple of releases).
		Revisions are fully optimized caches for revision control use.
		ext3) system who's accustomed to revision control systems designed with space efficiency as a higher-priority goal than a corruption-resistant repository format, arch will be relatively space-inefficient.
	freshmeat.net /releases/126189 (1572 words)

	FrontPage - Bazaar-NG
		Bazaar-NG is a decentralized revision control system designed to be easy for developers and end users alike.
		Revision Specs - Arguments for -r that can be given with "bzr log", "bzr merge" and such.
		If you're familiar with other version control systems, you might like to see a quick comparison to them, or read guidelines to help you understand how to use bzr most effectively given your current experience.
	bazaar-vcs.org (343 words)

	RCS4MPX Revision Control System (Site not responding. Last check: 2007-10-08)
		This Revision Control System (RCS) is an open system migration tool that permits the management of multiple revisions of files.
		If the revisions to be merged affect the same sections of code, RCS alerts the user about the overlapping changes.
		The identification (name, revision number, creation time, author, etc.) is like a stamp that can be embedded at an appropriate place in the text of a revision.
	www.jbsys.com /prod02.htm (574 words)

	ONLamp.com -- BSD Tricks: Introductory Revision Control
		Revision control is simply the process of tracking all changes made over time.
		Revision control allows a developer to see how a piece of code looked on a specific date, or an administrator to see how a daemon was configured before things stopped working.
		If you're not using revision control, you're making your work more difficult than it needs to be.
	www.onlamp.com /pub/a/bsd/2000/10/19/Big_Scary_Daemons.html (804 words)

	RCS - Revision Control System (basics) (Site not responding. Last check: 2007-10-08)
		Introduction ------------ The Revision Control System (RCS) is an efficient method of managing text files that are frequently revised, such as papers or program source code.
		The file that is being revised is known as the "working version", since it is being worked on.
		On subsequent revisions, RCS prompts for a log message which summarizes the changes to the file.
	www-acs.ucsd.edu /info/rcs.php (439 words)

	Version Control, Version Control Software, Document Version Control, Document Collaboration, Revision Control System
		Implementing WorldView's Version Control Module will increase productivity and efficiency, allowing users the luxury of working with applications they're familiar with, while providing organizations the luxury of a revision control system that stores all versions of their documents in one centralized repository.
		A complete audit trail is made with multiple revisions of a single document that enables users to efficiently view and reference specific revisions.
		Revision control settings can be assigned to various document types stored in the WorldView document management system, as well as specific users in your organization, for enhanced security control.
	www.worldviewltd.com /versioncontrol.html (604 words)

	Revision Control System (RCS) (Site not responding. Last check: 2007-10-08)
		Revisions can be retrieved by ranges of revision numbers, symbolic names, dates, authors, and states.
		If the revisions to be merged affect the same lines of a file, RCS flags the overlapping changes.
		Revisions can be assigned symbolic names and marked as released, stable, experimental, etc. With these facilities, configurations of a file can be described simply and directly.
	www.cse.dmu.ac.uk /~williams/report/node51.html (373 words)

	LWN: The Darcs Revision Control System
		Darcs is a relatively new revision control system that was written in Haskell by physicist David Roundy.
		Darcs is a revision control system, along the lines of CVS or arch.
		Darcs has two particularly distinctive features which differ from other revision control systems: 1) each copy of the source is a fully functional branch, and 2) underlying darcs is a consistent and powerful theory of patches.
	lwn.net /Articles/110516 (1183 words)

	CFST Help Page: Revision Control System (RCS) (Site not responding. Last check: 2007-10-08)
		RCS manages multiple revisions of text files by automating their storage, retrieval, logging, identification, and merging.
		RCS is useful for text that is revised frequently, for example programs, documentation,graphics, papers, form letters, etc. Any time you have a file which is periodically modified you should consider using RCS.
		This gives me the list of revisions in reverse chronological order, and what notes have been logged to the file after each revision.
	www.cse.ogi.edu /CFST/tut/rcs.html (1078 words)

	BitSCCS - SCCS compatible revision control system
		Both RCS and SCCS have comands for viewing revision history, but these commands (rlog and prs) work on a file at a time, i.e., first all the informationfrom one file, then the next, etc. Sccslog sorts the changes by time across all files, which is a much more intuitive way to view the data.
		User, revision, date, file name prefices - files may be viewed with any combination of the listed fields in front of each line in the file.
		There is a SCCS file browser which displays a graphical view of the file's revision history and gives you a text widget in which you can see revision history log entries, diffs, or any version of the file.
	www.bitmover.com /bitsccs (1139 words)

	RCS: Revision Control System (Site not responding. Last check: 2007-10-08)
		RCS is the Revision Control System for managing multiple revisions of files.
		The second is an RCS file, which is a compilation of all the differences between various revisions of a file.
		Revision 1.8 2001/01/04 05:45:34 nick ssi change, Revision 1.7 2000/06/18 19:39:36 nhertl made it ssi style Revision 1.6 2000/06/05 21:34:46 aschoonm A few _more_ minor edits...
	www.cs.hmc.edu /qref/rcs.html (906 words)

	Summary, Process-Based, STUVM, Definition Etc with Configuration Management Tool (Site not responding. Last check: 2007-10-08)
		Document control systems tend to focus more on the management of a large collection of documents and/or images, rather than on maintaining differing versions of a smaller number of documents.
		Document control systems are slowly replacing micro-fiche for archiving, and are used to store images of bank drafts (checks), land-survey data, engineering drawings, and the like.
		Because software change is often driven by problem reports, it is natural to integrate bug tracking systems with version control systems: this allows for a framework where changes resulting from a bug report can be easily located, and where some measure of certainty is provided that "all" changes have been integrated into a product release.
	www.configurationmanagement.org /configuration-management-tool.htm (2752 words)

	Concurrent Versions System, CVS, Tools for CVS, Revision Control, Build System Interacts With CVS (Site not responding. Last check: 2007-10-08)
		The Concurrent Versions System (CVS), also known as the Concurrent Versioning System, implements a version control system: it keeps track of all work and all changes in a set of files, typically the implementation of a software project, and allows several (potentially widely separated) developers to collaborate.
		The best way to do this with CVS (Concurrent Versions System) is to use the tag command to record which versions went into a given build (see section Tags--Symbolic revisions).
		Using CVS (Concurrent Versions System) in the most straightforward manner possible, each developer will have a copy of the entire source tree which is used in a particular build.
	www.version-control.info /concurrent-versions-system.htm (1383 words)

	Revision Control System (RCS) (Site not responding. Last check: 2007-10-08)
		Revisions can be retrieved according to ranges of revision numbers, symbolic names, dates, authors, and states.
		When two or more programmers wish to modify the same revision, RCS alerts the pro- grammers and prevents one modification from corrupting the other.
		Revisions can be assigned symbolic names and marked as released, stable, experimental, etc. With these facilities, configurations of modules can be described simply and directly.
	www.fortnet.org /FortNet/HTML/Presentation/CVS/rcsoview.html (178 words)

	Loads of Linux Links: Revision Control Systems
		Codeville - A Python-based, decentralized revision control system which allows updates from or commits to any repository at any time with no unnecessary re-merges.
		GNU arch - Revision control system similar to CVS and Subversion.
		Monotone - Distributed Version Control - A cross-platform version control system with a simple, single-file transactional version store, with fully disconnected operation, an efficient peer-to-peer synchronization protocol, cryptographic version naming and client-side RSA certificates and good internationalzation support.
	loll.sourceforge.net /linux/links/Programming_Links/Revision_Control_Systems (469 words)

	An ExpectTk/Perl Graphical User Interface to the Revision Control System (RCS)
		This script is used to initiate the revision control and update changes to the code in the revision control system.
		The STSDAS RCS system can be customized using two configuration files which control the colors of the GUI and the packages under revision control.
		The STSDAS RCS system may be obtained by contacting the author at ramon@stsci.edu.
	www.cv.nrao.edu /adass/adassVI/williamsonr.html (1189 words)

	Version Control with Subversion
		These systems are specifically tailored to manage trees of source code, and have many features that are specific to software development—such as natively understanding programming languages, or supplying tools for building software.
		The version control system often assists with the merging, but ultimately a human being is responsible for making it happen correctly.
		As you learned in the section called “Revisions”, a revision is a “snapshot” of the repository at a particular moment in time.
	svnbook.red-bean.com /en/1.0/svn-book.html#svn-ch-2-sect-3.1 (10617 words)

	The Project Revision Control System
		One simply checks in new versions as desired; the system will warn you if others have made parallel changes to the major version of the project you are working on that may have to be merged with changes you have made.
		Where PRCS differs from CVS (and, indeed, other source-code control systems of the author's acquaintance) is in its attempt to provide a particularly simple model to the user.
		Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
	www.cs.cmu.edu /~410/prcs-cmu/prcs.html (14905 words)

Try your search on: Qwika (all wikis)