Difference between revisions of "Version Control"
m (correct typo) |
(New page: Version Control is sometimes internal to a software application or tool. Users of OpenOffice Writer will be familiar with how you can open a document sent by a colleague, turn on "track c...) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Version Control is sometimes internal to a software application or tool. Users of | + | Version Control is sometimes internal to a software application or tool. Users of OpenOffice Writer will be familiar with how you can open a document sent by a colleague, turn on "track changes" and then your edits to the document will be clearly shown so that you can send the document back to the orginal author to provide feedback and the opportunity to merge changes in a friendly, efficient manner. |
Version Control in a software development environment is a large part of the infrastructure that makes software development possible -- because it provides the same feedback and opportunity to merge changes in a friendly, efficient manner. The tools that software developers use are CVS, [[Subversion]], Mercurial and Git or others. | Version Control in a software development environment is a large part of the infrastructure that makes software development possible -- because it provides the same feedback and opportunity to merge changes in a friendly, efficient manner. The tools that software developers use are CVS, [[Subversion]], Mercurial and Git or others. | ||
For distributed version control, merging and merge tracking including incorporation of "Third-party code" into your software products is really difficult or impossible with Subversion yet possible and even fun with Git. | For distributed version control, merging and merge tracking including incorporation of "Third-party code" into your software products is really difficult or impossible with Subversion yet possible and even fun with Git. | ||
| + | |||
# [[Subversion/Vendor Sources]] | # [[Subversion/Vendor Sources]] | ||
# [[Git/Vendor Sources]] | # [[Git/Vendor Sources]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Development]] | [[Category:Development]] | ||
[[Category:Subversion]] | [[Category:Subversion]] | ||
[[Category:Version Control]] | [[Category:Version Control]] | ||
Revision as of 17:31, 8 December 2008
Version Control is sometimes internal to a software application or tool. Users of OpenOffice Writer will be familiar with how you can open a document sent by a colleague, turn on "track changes" and then your edits to the document will be clearly shown so that you can send the document back to the orginal author to provide feedback and the opportunity to merge changes in a friendly, efficient manner.
Version Control in a software development environment is a large part of the infrastructure that makes software development possible -- because it provides the same feedback and opportunity to merge changes in a friendly, efficient manner. The tools that software developers use are CVS, Subversion, Mercurial and Git or others.
For distributed version control, merging and merge tracking including incorporation of "Third-party code" into your software products is really difficult or impossible with Subversion yet possible and even fun with Git.
