Atitit.eclipse git uses

Atitit.eclipse git uses

1 . Git vs SVN 1

1 . 1. Direct recording of snapshots, rather than differential comparisons 1

1 . 2. git patches are not dependent on the relationship between Branch,commit and commit is a graph 3

1 . 3. when HG is changed locally, you can pull the remote code directly and then merge it in the working directory of your current changes so that no additional branches are created 3

1 . 4. . Git in this case, you must commit or discard your local work, pull the remote code, and then merge the branches, that is, Git is forced to create the branch in this case. 3

1 . 5. git-based design: Each clone must contain a complete directory tree and a complete history, otherwise it cannot track further changes in the original warehouse 3

2 . of course, there are some drawbacks to git, and some of them might be more important: 4

2 . 1. User or create Respon in parent folder of PRJ 4

3 . Commit 4

1. Git vs SVN

Like SVN commits, push is completely catastrophic.

G  It need add,commit,then push to remote SVR.

HG commit code, the default is the current all changes. And Git has to add the current changes before commit.

1.1. Direct recording of snapshots, rather than differential comparisons

The main difference between Git and other version control systems is that git only cares about whether the overall file data is changing, while most other systems only care about the specific differences in file content. This type of system (Cvs,subversion,perforce,bazaar, etc.) records what files are updated each time, and what lines are updated, see figure 1-4.

Author :: ★ (Attilax) >>>    nickname : old-Wow paw   (   full name:: ATTILAX AKBAR AL RAPANUI&NBSP, Attilax &NBSP, " "  Al   Rapa Nui &NBSP,   Kanji name: Ayron, Email:[email protected]m

reprint Please indicate source: http://www.cnblogs.com/attilax/

Git does not store the variance data that changes before and after. In fact,Git is more like taking a snapshot of a changed file and recording it in a tiny file system. each time you submit an update, it will take a snapshot of all of the file's fingerprint information, and then save an index that points to the snapshot. To improve performance, if the file does not change, Git does not save it again, but only a link to the last saved snapshot. Git works as shown in Figure 1-5.

This is an important difference between Git and other systems. It completely overturned the traditional version control of the routine, and the implementation of the various aspects of the way to make a new design. Git is more of a small file system, but it also provides a number of 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 one months ago, Git takes the snapshot and the current file for one months to make a difference, instead of asking the remote server to do it, or pulling the old version of the file locally for comparison.

1.2. git patches are not dependent on the relationship between Branch,commit and commit is a graph

CVS 's patch is based on branch, and the relationship between patch and patch is aTREE. And git patches are not dependent on the relationship between Branch,commit and commit is aGRAPH. You can create different branch by stringing a commit in git with a different path.
It says here that patches don't cling to branch. Maybe some people don't understand that when submitting patches, they don't always commit and push on a development branch? Yes, butonce a commit is committed, it is no longer attached to the original branch, and becomes a discrete point in the repository ..
git's so-called branch, just in this star-studded lattice inside, draw a string of several commit lines.

1.3. when HG is changed locally, you can pull the remote code directly and then merge it in the working directory of your current changes so that no additional branches are created1.4. . Git in this case, you must commit or discard your local work, pull the remote code, and then merge the branches, that is, Git is forced to create the branch in this case. 1.5. git-based design: Each clone must contain a complete directory tree and a complete history, otherwise it cannot track further changes in the original warehouse

。 Specifically,
(1) It is difficult to directly track a subdirectory of a git repository: You must clone the entire repository and do subtree merge. SVN can checkout/update a subdirectory directly.
(2) Git is not applicable when changes are very large between each version. For example, you can use SVN to manage each version of binary release, the client can choose checkout which branch or tag, but if you use Git, you have to clone to local, which is crazy.

2. git has some drawbacks, of course, and some teams may still be more important:

1. Directory-level access control, allowing members to access only one directory ( usually a module );
2. intuitive version number;
3. partially 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..

Key Features of Git . html

Atitit.eclipse git uses