Before doing the project in the laboratory also used SVN, but little is known. Every update is submitted to it.
This time through this book, can be considered a formal study of the first off the concept under version control.
Also learned some knowledge of the GIT and github.
Content of the book
Overall, this book is a bit old.
If you want to learn fade SVN, Soso direct instructions, you can.
After all, now operating SVN pure command line has been very small, coupled with the widespread use of GIT, this book is a little out of the era.
But, after all, it is a programmer practice several essential books, or to learn a lot of things.
SVN's common operations
1 detection
This is the basic operation of the detection is to copy the code from the code library.
Update 2
In the conventional basis, to update the code.
3 submitted
The revised code, submitted to the code base.
SVN install and use
Spread
Due to the widespread use git, the number of SVN use some less, but there are still a lot of people use.
Whether the company or the project team, or an individual, there is a suitable code management tools are necessary.
Remember last year when the internship, I was careless eclipse right-delete multiple projects. The result is physically removed, I had to work overtime to write code again. And a lot of code due to a long time, have forgotten. This unnecessary overtime, but also makes me realize the need for version control.
In particular individual, on his own code management should be done very clear.
And not only it provides version control code storage, also provides various versions of the code quickly rolled back.
Rational use of these tools will enable developers to do more with less.
Reproduced in: https: //my.oschina.net/u/204616/blog/545251