subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 钱海远(Nathan) <>
Subject 答复: 答复: Can SVN pull request same as GIT?
Date Tue, 04 Dec 2018 09:11:50 GMT
Will you make any plan on SVN pull request?

More and more company change SCM system to Git.

Best Regards!
Haiyuan Qian
R & D Management Group
Hangzhou Hikvision Digital Technology Co.,Ltd
No.555 Qianmo Road, Binjiang District, Hangzhou 310052, China
T (86571)88075998-20081
M (86)18969199712

This e-mail and its attachments contain confidential information from HIKVISION, which is
intended only for  the person or entity whose address is listed above. Any use of the information
contained herein in any way (including, but not limited to, total or partial disclosure, reproduction,
or dissemination) by persons other  than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately and delete it!

发件人: Julian Foad []
发送时间: 2018年12月3日 16:48
收件人: 钱海远(Nathan); Nico Kadel-Garcia
抄送: Johan Corveleyn; Subversion
主题: Re: 答复: Can SVN pull request same as GIT?

钱海远(Nathan) wrote:
> [...]
> So we'd like to make a pre-commit CI system, if anyone who want to
> commit his code, we will build and test it first , if the CI passed the
> build and test , then it can merge to branches.
> We have 2 plan:
> Plan A ( 2015 we had make a linux svn issue plugin like this ,but it is
> easy ,just replace the svn program , see it at attachment):
> 1. Make a perl script to replace the svn program, rename svn bin to svn-
> org;
> 2. User can use svn commit command to commit his code ( in fact , the
> perl script will start) , the script will store the patches, and send it
> to our build system. Also script will start a daemon program work at
> user's computer to listen the build result.
> 3. When the build finished, daemon will tell user the result . We plan
> use svn mucc to commit the file ,then update the working copy.

I understand. Currently, Subversion supports patches that contain only a limited kinds of
changes -- text modifications, property modifications. In the future I hope we can provide
a patch format that supports all kinds of Subversion changes (copy, move, binary files, etc.).
The "Shelving" developments are providing some of the support that will be necessary to do

> Plan B (search it at google ):
> 1. Create a merge (pull) branch from the trunk and check that out.
> 2.Merge you development check-out branch into the "pull" branch.
> 3.Run test threads and do compares to verify the merge.
> 4.Integrate with the trunk.

Yes, that is the other main option.

Thank you for explaining this more clearly.

- Julian


This electronic message is intended to be viewed only by the individual or entity to whom
it is addressed. It may contain information that is privileged, confidential and exempt from
disclosure under applicable law. Any dissemination, distribution or copying of this communication
is strictly prohibited without our prior permission. If the reader of this message is not
the intended recipient, or the employee or agent responsible for delivering the message to
the intended recipient, or if you have received this communication in error, please notify
us immediately by return e-mail and delete the original message and any copies of it from
your computer system. For further information about Hikvision company. please see our website

View raw message