Shulou(Shulou.com)06/02 Report--

This article focuses on "what is the flow of Git distributed version control tools". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "what is the flow of Git distributed version control tools?"

1. The development of Git

Git was born in an era of great strife and innovation. The Linux kernel open source project has a large number of participants. Most of the maintenance work of the Linux kernel is spent on the tedious task of submitting patches and saving archives (1991 Murray 2002). By 2002, the entire project team began to enable a proprietary distributed version control system, BitKeeper, to manage and maintain code.

In 2005, the commercial company that developed BitKeeper ended its partnership with the Linux kernel open source community, and they took back the right of the Linux kernel community to use BitKeeper for free. This forces the Linux open source community (especially Linus Torvalds, the founder of Linux) to develop their own version of the system based on lessons learned when using BitKeeper.

2. Comparison between Git and SVN

SVN is a centralized version control system, and the version library is centrally placed on the central server, while developers use their own computers when they work, so first download the latest version from the central server, and then develop. After development, you need to submit your own developed code to the central server. The disadvantage of centralized version control tool is that the server has a single point of failure and poor fault tolerance. Git is a distributed version control system (Distributed Version Control System, referred to as DVCS), which is divided into two types of warehouses, local repositories and remote repositories. The local warehouse is the Git warehouse on the developer's own computer. A remote warehouse is a Git repository on a remote server.

3. The workflow of Git

(1) Clone the code from the remote warehouse to the local warehouse.

(2) checkout the code from the local warehouse and then modify the code.

(3) submit the code to the staging area before submitting.

(4) submit to the local warehouse. Each historical version of the modification is saved in the local warehouse.

(5) when you need to share the code with team members after the modification is completed, push the code to the remote warehouse.

At this point, I believe you have a deeper understanding of "what is the flow of Git distributed version control tools". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.