Git Introduction
In this post, we will learn the following.- what is git?
- why it became famous?
- why all are moving to Git?
- Git features?
In 2005, Initially Git has evolved by Linus Torvalds.
Every project must be using the Version Control. We are seeing everyone now migrating to Git.
Before moving into Git, first we will go through what is Version Control.
Problems before SVN:
1. If we do not have the Version Control then if any file is corrupted or lost then recovering the file is difficult and sometimes not possible.2. After reopening or recovering file if we want to move to previous state or compare with previous version, who last modified. These are not possible.
3. We have many issues like and difficult in maintenance hence introduced Version Control.
Examples: CVS, SVN, GIT, Mercurial, Bazaar, Monotone.
For Step-By-Step explanation, Click on how to unstage a file from git.
Why moving to Version Control:
4. Version Control is the process that records every change happens to the file over time.5. This can be done for a file or a set of files. In fact, every project is set of files with many folders.
6. If we want to move to a specific time what change was done to the file can be seen.
7. Comparing changes that have been modified or introducing issues.
8. We can revert to the older version of file or previous state of the project which is stable version in case of issues.
Git feature are:
9. Git follows a simple design flow. Easily understand by all.10. Solid support for working with parallel branches (can be multiples of 100).
11. Fully distributed version control. If Git repository is destroyed, we will have still copy in our local machine which can be placed in our server so that it behaves as master.
12. Works in windows and Unix efficiently.
13. Speed: Git is very very fast than any other Version Control in the market. It supports for bulk commits, checkout very fast with no flaws.
Important points on Git:
14. Git follows distributed mechanism.
15. The server stores all changes mean all versions (modification over time) of file.
16. Once we do checkout the project it just does not download the only latest version of copy from server, it copy or mirror the full repository.
17. If the server dies or corrupted then we can get the fully mirrored copy from any of the client’s machine which they had cloned from repository.
18. We can say every cloned copy is full back up of server repo but there might be missing some versions if any client made commits.
19. In Git, We can create multiple sub branches from main or master branch.
20. In real time, usually for every change there will be branch which is created from maser for the change and these branch changes will be merged back to the master.
No comments:
Post a Comment
Please do not add any spam links in the comments section.