On Thu, Nov 29, 2018 at 10:31 PM 钱海远(Nathan) <qianhaiy...@hikvision.com> wrote:
> Dear Sir, > > > > We want to develop a feature like git pull request . > > > > But it is not easy to develop. Svn has only one server , how to store the > patches? If build failed , how to revert working copy. How to resolve the > conflict. > > > > Git is a better , it can support pre-commit code review, pull request by > default. Is subversion able to develop these features in the future?. > > > > We like subversion ,we build a lot tools for subversion, like the > pre-commit code review、issue plugin、code count、svn multisite (same as > Wandisco’s svn multisite plus) ,but it’s became hard and hard, is it time > for us to give up svn? > > > This seems infeasible. The working copy in which the merges would occur does not exist in the Subversion workflow. It's a case where git-svn could work well, as long as you avoid the boobytraps such as difficulties merging metadata, such as "svn:keywords" or ".gitattributes" or features like submodules.
