Git and svn are both relatively mainstream version control tools. As an intern, it is recommended that you have a basic understanding of both.
Their role is to manage code and version control, which helps in code protection and collaborative development among team members.
The difference between them is simply the difference in management methods. The reflection in actual use is that svn can relatively easily implement single-line version control and conveniently resolve code conflicts. Git is relatively more convenient to implement flexible branch management.
At present, both of them have relatively complete information for learning on the Internet, and they are relatively easy to master.
If possible, you should learn them all. After all, there are never too many techniques, especially useful ones. Moreover, you are not sure what your future company will use. A more comprehensive grasp will make your path to finding a job wider.
1. vcs (version control system) is an indispensable tool in development, and it is necessary to master it. It is embarrassing and inappropriate to say that you don’t know CVS during an interview.
2. There are many implementations of vcs, such as git/svn/tfs. Each cvs has different implementation ideas and different usage experience. For example, tfs/svn is a vcs that relies on a central server, and git is a distributed vcs, so git works faster than tfs/svn.
3. You may need to establish a skill to quickly understand and learn a technology. Of course, this is closely related to development experience, but experience is accumulated slowly and is not a day's work.
4. If you have strong self-learning ability, it is recommended to learn git directly, git book, and git pro are all good teaching materials, which not only include git knowledge, but also an introduction to CVS ideas. In addition, there are many other learning resources, such as QQ groups, laboratory buildings, many open classes, blogs, etc.
5. Git is a very popular CVS and has a strong community. Experience tells me that the community is an important resource for learning development technology, and communication makes developers progress. Learning with a community is fundamentally different from learning without a community. In addition, in the process of learning git, you can directly use the service of github.com to host the code on the github server.
Learn git. I would be embarrassed to say that you are a computer major without mentioning distributed technology. If you want to learn git information, I have compiled it on github. Currently, it has 580+ stars and 170+ forks. Personally, it feels good. Address: https://github.com/xirong/my-git
Version control records changes to each module of the program through document control and serializes each change. This method is a standard practice for maintenance of engineering drawings, and it accompanies engineering drawings from the birth of the drawing to the finalization of the drawing. A simple form of version control, for example, assigning a version grade "A" to the first version of a diagram. When the first change is made, the version grade changes to "B", and so on. http://baike.baidu.com/view/183136.htm
Use git.
We used svn before to develop the main trunk and branch the online version. In this model, a version is released once a week, or once every two weeks, which is all kinds of pain.
Now I switch to git, strictly follow the git work flow, one version every day, various patches, all kinds of fun.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
If you use GitHub instead of visiting forums or WeChat Moments, you will basically be familiar with git. . .
Git and svn are both relatively mainstream version control tools. As an intern, it is recommended that you have a basic understanding of both.
Their role is to manage code and version control, which helps in code protection and collaborative development among team members.
The difference between them is simply the difference in management methods. The reflection in actual use is that svn can relatively easily implement single-line version control and conveniently resolve code conflicts. Git is relatively more convenient to implement flexible branch management.
At present, both of them have relatively complete information for learning on the Internet, and they are relatively easy to master.
If possible, you should learn them all. After all, there are never too many techniques, especially useful ones. Moreover, you are not sure what your future company will use. A more comprehensive grasp will make your path to finding a job wider.
Teacher Liao Xuefeng’s git tutorial: git complete tutorial
1. vcs (version control system) is an indispensable tool in development, and it is necessary to master it. It is embarrassing and inappropriate to say that you don’t know CVS during an interview.
2. There are many implementations of vcs, such as git/svn/tfs. Each cvs has different implementation ideas and different usage experience. For example, tfs/svn is a vcs that relies on a central server, and git is a distributed vcs, so git works faster than tfs/svn.
3. You may need to establish a skill to quickly understand and learn a technology. Of course, this is closely related to development experience, but experience is accumulated slowly and is not a day's work.
4. If you have strong self-learning ability, it is recommended to learn git directly, git book, and git pro are all good teaching materials, which not only include git knowledge, but also an introduction to CVS ideas. In addition, there are many other learning resources, such as QQ groups, laboratory buildings, many open classes, blogs, etc.
5. Git is a very popular CVS and has a strong community. Experience tells me that the community is an important resource for learning development technology, and communication makes developers progress. Learning with a community is fundamentally different from learning without a community. In addition, in the process of learning git, you can directly use the service of github.com to host the code on the github server.
Good git learning materials: http://git-scm.com/book/zh/v1%E3%80%81
Learn git. I would be embarrassed to say that you are a computer major without mentioning distributed technology. If you want to learn git information, I have compiled it on github. Currently, it has 580+ stars and 170+ forks. Personally, it feels good. Address: https://github.com/xirong/my-git
Version control records changes to each module of the program through document control and serializes each change. This method is a standard practice for maintenance of engineering drawings, and it accompanies engineering drawings from the birth of the drawing to the finalization of the drawing. A simple form of version control, for example, assigning a version grade "A" to the first version of a diagram. When the first change is made, the version grade changes to "B", and so on.
http://baike.baidu.com/view/183136.htm
You should say: "This is just a fucking tool, just like a hammer. I can use it when I pick it up."
Contribute Git Collection Simple Guide
Use git.
We used svn before to develop the main trunk and branch the online version. In this model, a version is released once a week, or once every two weeks, which is all kinds of pain.
Now I switch to git, strictly follow the git work flow, one version every day, various patches, all kinds of fun.