{"id":28,"date":"2017-09-24T03:54:53","date_gmt":"2017-09-24T03:54:53","guid":{"rendered":"http:\/\/www.sureshselvam.com\/?p=28"},"modified":"2021-04-27T12:40:18","modified_gmt":"2021-04-27T12:40:18","slug":"git-version-control-system","status":"publish","type":"post","link":"https:\/\/www.sureshselvam.com\/index.php\/2017\/09\/24\/git-version-control-system\/","title":{"rendered":"GIT (Version Control System)"},"content":{"rendered":"

What is Version Control?<\/strong><\/p>\n

\"git\"<\/a><\/p>\n

Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.
\nIt allows you to revert files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more.<\/p>\n

Local Version Control Systems<\/strong>
\nMany people\u2019s version-control method of choice is to copy files into another directory
\nIt is easy to forget which directory you\u2019re in and accidentally write to the wrong file or copy over files you don\u2019t mean to.
\nTo deal with this issue, programmers long ago developed local VCSs that had a simple database that kept all the changes to files under revision control.
\nOne of the more popular VCS tools was a system called RCS
\nRCS works by keeping patch sets (that is, the differences between files) in a special format on disk; it can then re-create what any file looked like at any point in time by adding up all the patches.<\/p>\n

Centralized Version Control Systems<\/strong><\/p>\n

Need to collaborate with developers on other systems.
\nCentralized Version Control Systems (CVCSs) were developed. These systems, such as CVS, Subversion.
\nFor many years, this has been the standard for version control.
\n\u00a0Administrators have fine-grained control over who can do what; and it\u2019s far easier to administer a CVCS than it is to deal with local databases on every client.
\nThis setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents.
\nServer goes down for an hour
\n\u00a0If the hard disk the central database is on becomes corrupted, and proper backups haven\u2019t been kept<\/p>\n

Distributed Version Control Systems<\/strong><\/p>\n

In a DVCS (such as Git), clients don\u2019t just check out the latest snapshot of the files: they fully mirror the repository.
\nThus if any server dies, and these systems were collaborating via it, any of the client repositories can be copied back up to the server to restore it.
\nEvery clone is really a full backup of all the data.<\/p>\n

GIT<\/strong><\/p>\n

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
\nGit is a version control system that is used for software development and other version control tasks. As a distributed revision control system it is aimed at speed, data integrity, and support for distributed, non-linear workflows. Git was created by Linus Torvalds in 2005 for development of the Linux kernel, with other kernel developers contributing to its initial development.<\/p>\n

Some of the goals of the new system were as follows:<\/strong>
\nSpeed
\nSimple design
\nStrong support for non-linear development (thousands of parallel branches)
\nFully distributed
\nAble to handle large projects like the Linux kernel efficiently (speed and data size)<\/p>\n","protected":false},"excerpt":{"rendered":"

What is Version Control? Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. It allows you to revert files back to a previous state, revert the entire project back to a previous state, compare changes over time, see who last modified something that might be causing a problem, who introduced an issue and when,…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-28","post","type-post","status-publish","format-standard","hentry","category-git"],"_links":{"self":[{"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/posts\/28","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/comments?post=28"}],"version-history":[{"count":5,"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/posts\/28\/revisions"}],"predecessor-version":[{"id":35,"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/posts\/28\/revisions\/35"}],"wp:attachment":[{"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/media?parent=28"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/categories?post=28"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sureshselvam.com\/index.php\/wp-json\/wp\/v2\/tags?post=28"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}