Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:49:35Z

Science: /* External Links */

== History of Version Control ==

[http://en.wikipedia.org/wiki/Revision_control Version Control] (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN])is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

== References ==

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

== External Links ==

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:49:17Z

Science: /* References */

== History of Version Control ==

[http://en.wikipedia.org/wiki/Revision_control Version Control] (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN])is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

== References ==

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:36:48Z

Science: /* ''References'' */

== History of Version Control ==

[http://en.wikipedia.org/wiki/Revision_control Version Control] (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN])is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:35:49Z

Science: /* References */

== History of Version Control ==

[http://en.wikipedia.org/wiki/Revision_control Version Control] (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN])is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== ''References'' ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:33:21Z

Science: /* History of Version Control */

== History of Version Control ==

[http://en.wikipedia.org/wiki/Revision_control Version Control] (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN])is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:33:02Z

Science: /* History of Version Control */

== History of Version Control ==

[http://en.wikipedia.org/wiki/Revision_control Version] Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN])is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:30:54Z

Science: /* Subversion (SVN) */

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN])is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:30:28Z

Science: /* Subversion (SVN) */

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion[http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:29:43Z

Science: /* Subversion (SVN) */

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion[http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN)is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:29:21Z

Science: /* Subversion (SVN) */

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion([http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN)is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:26:29Z

Science: /* Concurrent Version System (CVS) */

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK ([http://tack.sourceforge.net/ Amsterdam Compiler Kit]) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:24:15Z

Science: /* Concurrent Version System (CVS) */

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [http://www.nongnu.org/cvs/ CVS]. He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:23:17Z

Science: /* Concurrent Version System (CVS) */

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System [(http://www.nongnu.org/cvs/CVS)]. He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:16:44Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

=== Concurrent Version System (CVS) ===

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

==== Limitations of CVS: ====

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

=== Subversion (SVN) ===

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

=== Academic Papers Related to Version Control ===

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

=== References ===

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

=== External Links ===

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:14:53Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

=== Revion Control System (RCS) ===

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

==== Limitations of RCS: ====

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:14:24Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

=== Source Code Control System (SCCS) ===

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:08:40Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System ([http://www.gnu.org/software/rcs/ RCS]) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T03:07:52Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System ([http://en.wikipedia.org/wiki/Source_Code_Control_System SCCS]) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System (RCS) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T02:23:12Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System (SCCS) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System (RCS) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] [http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS]

[3] [http://en.wikipedia.org/wiki/Subversion_%28software%29 SVN]

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T02:21:40Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System (SCCS) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System (RCS) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] [http://www.cs.vu.nl/~dick/CVS.html#Books Dick Grune on CVS]

[2] http://en.wikipedia.org/wiki/Concurrent_Versions_System

[3] http://en.wikipedia.org/wiki/Subversion_%28software%29

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T02:20:48Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work stored electronically. Before the advent of electronic storage, a hard copy (such as on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both - possible and a necessity to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity. A brief look at the earlier generations of Version Control Software.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System (SCCS) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System (RCS) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] http://www.cs.vu.nl/~dick/CVS.html#Books

[2] http://en.wikipedia.org/wiki/Concurrent_Versions_System

[3] http://en.wikipedia.org/wiki/Subversion_%28software%29

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T02:14:02Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work which is stored electronically. Before the advent of electronic storage, a hard copy (such as those on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both possible and necessary to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System (SCCS) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System (RCS) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] http://www.cs.vu.nl/~dick/CVS.html#Books

[2] http://en.wikipedia.org/wiki/Concurrent_Versions_System

[3] http://en.wikipedia.org/wiki/Subversion_%28software%29

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

[http://www.cvsnt.org/manual/html/CVS-commands.html CVS Commands]

[http://www.linuxfromscratch.org/blfs/edguide/chapter03.html SVN Commands]

[http://betterexplained.com/articles/a-visual-guide-to-version-control/ Visual Guide to Version Control]

[http://www.nongnu.org/cvs/ CVS on Web]

[http://www.developingprogrammers.com/index.php/2005/11/24/cvs-and-subversion-combined-tutorial/ CVS-SVN Tutorial]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T02:09:14Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work which is stored electronically. Before the advent of electronic storage, a hard copy (such as those on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both possible and necessary to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System (SCCS) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System (RCS) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

'''References'''

[1] http://www.cs.vu.nl/~dick/CVS.html#Books

[2] http://en.wikipedia.org/wiki/Concurrent_Versions_System

[3] http://en.wikipedia.org/wiki/Subversion_%28software%29

'''External Links'''

[http://agave.garden.org/~aaronh/rcs/manual/peter_ware-1987/rcs_3.html RCS Commands]

[http://www.gnu.org/software/rcs/ RCS on GNU]

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T02:07:03Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is a category of software whose purpose is to manage changes to digital information in an automated way. Digital information, in this context could be source code of computer programs, design database or any other piece of work which is stored electronically. Before the advent of electronic storage, a hard copy (such as those on paper) was automatically granted as preserved. With storage getting shifted on to electronic media, it became both possible and necessary to have software which could keep track of changes to the information stored.

Today, with development project typically spanning multiple geographical sites and people with different time schedules, Version Control program have become a necessity.

'''Source Code Control System (SCCS) '''

One of the earliest revision control software, Source Code Control System (SCCS) was developed at [http://en.wikipedia.org/wiki/Bell_Labs Bell Labs] in 1972 by Marc Rochkind. Though initially written for [http://en.wikipedia.org/wiki/System/370 IBM System/370] computer, it was later re-written for UNIX and subsequently included in several UNIX distributions. SCCS remained the dominant version control system until Revision Control System (RCS) was released. Today, SCCS is considered obsolete; the file format of SCCS is still used by some revision control programs like [http://en.wikipedia.org/wiki/BitKeeper BitKeeper] and [http://en.wikipedia.org/wiki/TeamWare TeamWare].

'''Revion Control System (RCS)'''

Revion Control System (RCS) was developed by [http://www.ipd.uka.de/~tichy/ Walter F. Tichy] in the 1980s while he was at the Purdue University. RCS was an improvement when compared to SCCS. It had a better user interface and the method of storage resulted in faster retrieval. It stored the most recent file in entirety. The earlier revisions of the file was stored as reverse differences. This feature made it operate faster than SCCS. RCS was made freely available. It quickly dislodged SCCS from its dominant position and became part of the GNU Project. Last maintenance on RCS was in 1995.

'''Limitations of RCS:'''

- It could only work on single files, not on on project or hierarchies(directories).

- At any given time, only one person could edit a file .

- It was not possible to group together files.

- RCS directory had to be local.

'''Concurrent Version System (CVS)'''

[http://www.cs.vu.nl/~dick/ Dick Grune] of Vrije University, Amsterdam created Concurrent Version System (CVS). He created it so that he could cooperate with two of his students while working on ACK (Amsterdam Compiler Kit) C compiler [1]. CVS used the Client-Server architecture where the server was used as the repository. CVS could handle multiple people working on a set of files simultaneously without resulting in any conflicts. The server was used to store the current version of the project. When someone wants to modify one or more files, he has to check it out, modify and then check-in. The server stored all the relevant information, like revision history, revisions of projects/files, historical snapshot of the project etc. Clients can request these information as needed. Typically, the client and server communicate over LAN or internet. However, this is not a necessity as the client and server could be hosted on the same machine. CVS was initally created calling RCS programs. This was later changed as further refinement. More on CVS can be found in [2].

'''Limitations of CVS:'''

- A commit was not an [http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29 atomic operation].

- File(s) or directory renaming is not version controlled.

- Handling binary files is (processor/bandwidth) expensive.

- Cost is proportional to data size.

'''Subversion (SVN)'''

Subversion is a version control software introduced in 2000. It is the outcome of an effort to develop an open source version control system to succeed CVS by adding the missing features (in CVS) and fixing the bugs. Subversion is released under the [http://en.wikipedia.org/wiki/Apache_License Apache License], making it open source. SVN has become quite popular and has been adopted in the corporate world as well. More on SVN can be found in [3].

'''Academic Papers Related to Version Control'''

1. Marc J. Rochkind. “The Source Code Control System”. 364-370. IEEE Transactions on Software Engineering. SE-1. 4. Dec 1975.

2. Walter F. Tichy. ““Design, Implementation, and Evaluation of a Revision Control System””. 58-67. Proceedings of the 6th International Conference on Software Engineering. ACM. IEEE. IPS. NBS. . September 1982.

3. Stuart I. Feldman. 255-265. “Make—A Program for Maintaining Computer Programs”. Software—Practice & Experience. 9. 3. March 1979.

4. James W. Hunt and M. D. McIlroy. “An Algorithm for Differential File Comparison”. 41st Computing Science Technical Report. Bell Laboratories. June 1976.

5. Alan L. Glasser. ““The Evolution of a Source Code Control System””. 122-125. Software Engineering Notes,. 3. 5. Nov. 1978. Proceedings of the Software Quality and Assurance Workshop.

6. A. Nico Habermann. A Software Development Control System. Technical Report. Carnegie-Mellon University, Department of Computer Science. Jan. 1979.

7. Walter F. Tichy. ““A Data Model for Programming Support Environments and its Application””. Automated Tools for Information System Design and Development. Hans-Jochen Schneider. Anthony I. Wasserman. North-Holland Publishing Company. Amsterdam. 1982.

8. Walter F. Tichy. “The String-to-String Correction Problem with Block Moves”. ACM Transactions on Computer Systems. 2. 4. 309-321. Nov. 1984.

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:55:44Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:43:56Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:39:41Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:39:30Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:39:10Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:38:15Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:37:47Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:36:26Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:26:10Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:06:54Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T01:05:44Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:59:58Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:57:27Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:52:47Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:51:40Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:51:28Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:51:08Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:50:51Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:49:19Z

Science:

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:39:44Z

Science:

== History of Version Control ==

Version Control (also called Revision Control, Source Code Control) is the name given to a category of software whose purpose is to manage changes to digital information in an automated fasion. Version Control software is used in all types of industry where the people work on computer files. Few examples of the types of these files are source code (e.g., in software development), design database (e.g., in semiconductor industry) etc. Today, revision control has become an integral part of the development especially with multiple people located at different geographical locations (and time zone) collborating on the same project.

CSC/ECE 517 Fall 2009/wiki1a 5 a2

2009-09-08T00:39:06Z

Science:

== History of Version Control ==