Atitit. eclipse git, atitit. eclipsegit

Atitit. eclipse git, atitit. eclipsegit

Atitit. eclipse git usage

 

 

1. Git vs svn1

1.1. Directly record snapshots, rather than comparison 1

1.2. The Git patch is not attached to branch. The relationship between commit and commit is a GRAPH3

1.3. If there is a local change to hg, you can directly run the pull remote code, and then merge it in the working directory you are changing so that no additional branch 3 is created.

1.4 .. In this case, git must submit or discard its local work, then pull remote code, and then merge the branches. That is to say, git is forced to create branches in this case. 3

1.5. git-based design: Each clone must contain a complete directory tree and a complete history; otherwise, further changes to the original repository cannot be tracked. 3

2. Of course, git also has some shortcomings, and some teams may pay more attention to it: 4

2.1. User or create respon in parent folder of prj4

3. Commit4

 

1. Git vs svn

Like svn, commit means push is a complete disaster.

Git need add, commit, then push to remote svr.

When the hg commit code is used, all changes are made by default. Git must add the current modification before commit.

 

1.1. Directly record snapshots, rather than compare differences

The main difference between Git and other version control systems is that Git only cares about whether the overall file data changes, while most other systems only care about the specific differences in file content. This type of system (CVS, Subversion, Perforce, Bazaar, etc.) records the files that have been updated and the rows that have been updated. See figure 1-4.

 

Author ::★(Attilax)> nickname: old wow's paw (full name: Attilax Akbar Al Rapanui Attila Akba Arla Panui) Chinese name: AI long, EMAIL: 1466519819@qq.com

Reprinted please indicate Source: http://www.cnblogs.com/attilax/

 

Git does not store the different data before and after the changes. In fact, Git takes snapshots of changed files and records them in a micro file system. Each time an update is submitted, it will view the fingerprint information of all files and take a snapshot of the file, and then save an index pointing to the snapshot. To improve performance, if the file remains unchanged, Git will not save it again, but only make a link to the last saved snapshot. Git works like Figure 1-5.

 

 

 

 

This is an important difference between Git and other systems. It completely subverts the traditional version control routines and designs the implementation methods of each link. Git is more like a small file system, but it also provides many powerful tools based on this, not just a simple VCS.

 

. If you want to see the difference between the current version of the file and the version earlier than a month ago, Git will take out the snapshot a month ago and perform a Difference Operation on the current file, instead of requesting a remote server to do this, or pulling files of earlier versions to a local directory for comparison.

1.2. The Git patch is not attached to branch. The relationship between commit and commit is a GRAPH

 

In comparison with CVS, The CVS patch is based on branch, and the relationship between patch and patch isTREE. The Git patch is not attached to branch, and the relationship between commit and commit isGRAPH.Different branchs can be formed by concatenating the commit in Git in different paths.
Here we can say that the patch is not attached to branch. Some people may not understand it. When submitting the patch, isn't it always on a Development branch to commit and push it? Yes,Once submitted, a commit is no longer attached to the original branch and becomes a discrete point in the repository..
The so-called branch in Git is just to draw a string of several commit lines in this dense dot matrix.

1.3. If there is a local change to hg, you can directly run the pull remote code, and then merge the code in the working directory you are changing, so that no additional branch is created.1.4. . In this case, git must submit or discard its local work, then pull remote code, and then merge the branches. That is to say, git is forced to create branches in this case.1.5. Git-based design: Each clone must contain a complete directory tree and a complete history. Otherwise, further changes to the original repository cannot be tracked.

. Specifically,
(1) It is difficult to directly track a subdirectory of the git Repository: You must clone the entire repository and then create a subtree merge. SVN can directly checkout/update a subdirectory.
(2) git is not applicable when each version changes greatly. For example, you can use svn to manage various versions of binary release. The client can choose which branch or tag to checkout. But if you use git, You Have To clone it to the local directory first, which is crazy.

2. Of course, git also has some shortcomings, which may be important to some teams:

1. Directory-level access control allows some members to access only one directory (usually a module );
2. Intuitive version number;
3. Check out a directory, usually a module/branch;

 

2.1. User or create respon in parent folder of prj

 

 

Create repos workspace \. git

 

 

3. Commit

First add to index

Then commit ..

Bier yva file yao ni select l ..

 

 

Git key points. html