[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-users
Subject:    =?utf-8?B?562U5aSNOiDnrZTlpI06IENhbiBTVk4gcHVsbCByZXF1ZXN0IHNhbWUgYXMg?= =?utf-8?Q?GIT=3F?=
From:       钱海 <qianhaiyuan () hikvision ! com>
Date:       2018-12-04 9:11:50
Message-ID: a4d51ab94bcc449aa3c56b19e57f0ef2 () hikvision ! com
[Download RAW message or body]

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 [mailto:julianfoad@apache.org]
发送时间: 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 that.

> 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

________________________________
CONFIDENTIALITY NOTICE:

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 at \
www.hikvision.com<http://www.hikvision.com>


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic