Skillfully use the SVN create patch (Patch) solution to address the needs of the customized version

Recently the project customization version more and more, maintenance, synchronization code very troublesome. Previous ideas such as:

The previous SVN directory structure is as follows:

There are 2 such questions:

• If you fix a bug in a custom package that other custom packages have, it's very laborious + mechanical to update the code of other packages, and it's easy to make manual mistakes.
• If a custom replacement person maintenance, the new person, the handover time, and the new people easy to forget the key points, the custom version on the basis of the main version of the changes can not remember.

As a result, I studied the svn create/apply patch feature, because the SVN patch format file can faithfully record the file changes, so the 2nd problem mentioned above is solved, and the new scheme has only one main version, Fixing any common bugs only needs to be fixed in the main version, eliminating the need to synchronize the code, and issue 1 can be resolved. So, the new idea is: the main version of the +patch package = Custom version, SVN only "main version" and "Patches" 2 source code directory

Reference copy:

Creating and applying patches for create in SVN http://blog.sina.com.cn/s/blog_734073c90100p43t.html

New ideas for improvement such as:

SVN directory structure such as:

Patches directory contents such as:

This article ends.

Skillfully use the SVN create patch (Patch) solution to address the needs of the customized version