Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Revision control

Related Topics

  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.
One of the leading proponents of distributed revision control is Linus Torvalds, developer of the Linux kernel.
en.wikipedia.org /wiki/Revision_control   (1423 words)

 Revision Control System manpage   (Site not responding. Last check: 2007-11-06)
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)

 [No title]   (Site not responding. Last check: 2007-11-06)
Part (or circuit schematic) revision is noted on each module by either a brady marker or a red stamp on the end of the module handle.
The option will be considered compatible with the current kernel hardware, VMS and microcode revisions, assuming that is what was used during the development of the option.
The KC730 hardware that will be kept under revision control consists of two PROMS that reside (when used) on the WCS board (M8394), in chip locations E50 and E52.
deathrow.vistech.net /~cvisors/DEC94MDS/11725rva.txt   (1586 words)

 np237: On distributed revision control systems   (Site not responding. Last check: 2007-11-06)
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)

 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-11-06)
arch is a revision control system with features that are ideal for free software and open source projects characterized by widely distributed development, concurrent support of multiple releases, and substantial amounts of development on branches.
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)

 Ch 23 -- Introduction to Revision Control   (Site not responding. Last check: 2007-11-06)
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.
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.
When the project hits a milestone, you can either synchronize all of the file's revision numbers (bring them all to the same level, such as 1.7) or increase the major version number of the next revision (the next change for all of the files is checked in at 2.1).
docs.rinet.ru /UNIXi/ch23.htm   (3760 words)

 Revision Control with Arch: Introduction to Arch | Linux Journal   (Site not responding. Last check: 2007-11-06)
Revision control is the business of change management within a project.
A new generation of revision control systems has sprung up in the past few years, all operating on a distributed model.
Distributed revision control systems do away with a single centralized repository in favor of a peer-to-peer architecture.
www.linuxjournal.com /article.php?sid=7671   (2926 words)

 Palimpsest: A Data Model for Revision Control   (Site not responding. Last check: 2007-11-06)
By basing the fundamental structures of Palimpsest on the individual changes (or deltas) made to the shared data at a fine grain, a wide variety of revision management strategies can be represented, while the scope of possible conflicts is reduced to the smallest possible portion of the document.
A similar approach is the use of file difference algorithms to track the revision process as in [16].
The general idea of basing configuration or version control around changes to data rather than states of data has been suggested previously in the software engineering literature (see [12, 13]), but Palimpsest presents many significant differences from this work.
cs-people.bu.edu /dgd/thesis/original_paper.html   (5395 words)

 Free Source Code Version Control Software (Revision Control Software) (thefreecountry.com)
GNU RCS is a revision control system that allows you to manage multiple versions of your source code in a space efficient manner.
This is a source control and versioning system that is written in Java, and as such should be able to run on any system that has a Java virtual machine.
This is a front end to a set of revision control tools that is supposed to be simpler to use than RCS, SCCS and CVS.
www.thefreecountry.com /programming/versioncontrol.shtml   (1607 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)

 CS 2335 - Lab 1
Revision Control System (RCS) incorporates a "smart" system of saving versions of code while under development so that an error can be recovered from any modified version of the software currently under version control.
Source control can allow you to specify what file revision you want to start with, and also how the revision of the file you're creating will relate to the ones that already exist.
Control of file modification - In most cases, it is important to ensure that two developers can't modify the same revision of any file simultaneously.
www.cc.gatech.edu /computing/classes/AY2001/cs2335_spring/Labs/lab1.html   (2862 words)

 Revision Control System   (Site not responding. Last check: 2007-11-06)
When the project is created, the type of revision control can be chosen in the New Project dialog with the help of Revision Control drop-down combo-box.
The revision control type of the folder being added should be chosen with the help of Revision Control combo-box of the Create New Folder dialog.
The same dialog is appear when you are manually pressing "Fetch sources" button in the Revision Control label of the Node Properties dialog.
www.codeforge.com /help/RCS.html   (1422 words)

 RCS—A System for Version Control
The initial revision is the root of the tree, and the tree edges indicate from which revision a given one evolved.
In experimental environments, where strong controls are counterproductive, it is possible to loosen the controls.
Revision groups of individual components are treated in the next three sections, and the extensions to configurations follow.
www.uvm.edu /~ashawley/rcs/tichy1985rcs/html   (488 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)

 Detailed Change Control Procedure
Informal revision control refers to the use of tools which allow changes to a rapidly evolving work product to be sequentially captured and retraced, if necessary.
Revision control differs from change control in that it provides automated support for saving and restoring versions of project work products such as documents and computer source code without the burden of a formal change process.
Since change control at this stage of development is informal, it is the responsibility of each developer to use prudent judgment and professional practice to store revisions of the work product at appropriate intervals and to be diligent in maintaining master sources of the work product on the project file server.
www.construx.com /survivalguide/detailedchangeproc.htm   (1874 words)

The goal of the Subversion project is to build a version control system that is a compelling replacement for CVS in the open source community.
Revision numbers are per-commit, not per-file; log messages are attached to the revision, not stored redundantly as in CVS.
Subversion is equally efficient on binary as on text files, because it uses a binary diffing algorithm to transmit and store successive revisions.
subversion.tigris.org   (637 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)

 Survey of Version Control Tools
In particular, it is impractical to compare several old revisions of a group, because that may require mounting and searching several tapes.
SCCS stores multiple revisions of source text in an ancestral tree, records a log entry for each revision, provides access control, and has facilities for uniquely identifying each revision.
The revisions of a module are only distinguished by creation time, and there is no tool for managing groups.
www.uvm.edu /~ashawley/rcs/tichy1985rcs/html/ar01s07.html   (998 words)

 RCS - Revision Control System (basics)   (Site not responding. Last check: 2007-11-06)
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 /offerings/userhelp/OLD_HTML/rcs,d.html   (455 words)

 Using Revision Control with Wing
This version of Wing introduces a simple revision control integration facility that is useful for the most common revision control operations, but is currently only available for CVS (the Concurrent Versions System).
This is a preliminary integration of revision control with Wing that is based on the IDE's new scripting extension API.
Additional revision control systems will be added in the future and tighter integration with the project manager are planned.
wingware.com /doc/edit/revision-control   (637 words)

 RCS: Revision Control System   (Site not responding. Last check: 2007-11-06)
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)

 Applying RCS and SCCS: From Source Control to Project Control: Chapter 3: Basic Source Control Using RCS
Revision Control System, or RCS, was developed by Walter F. Tichy at Purdue University in the early 1980s.
It also uses the term "check-in" to refer to the addition of a new revision to an RCS file and "check-out" to refer to the retrieval of an existing revision from an RCS file.
Now that you have the lock, you have the exclusive right to change this revision (revision 1.1) of the file and eventually to check in your working file as the next revision of the RCS file.
www.oreilly.com /catalog/rcs/chapter/ch03.html   (4531 words)

 Revision Control
AutoEDMS' revision control is completely configurable, very comprehensive and can be fine-tuned to match each clients requirements.
Any number of revisions can be kept on-line for viewing and copying, but only the current revision will be available for editing.
Different revision control standards can be implemented for different types of files, controlled vs. uncontrolled files, etc.
www.acssoftware.com /html/revision_control.html   (302 words)

Try your search on: Qwika (all wikis)

  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.