On Fri, Nov 30, 2018 at 8:20 AM Julian Foad wrote:
>
> Nico Kadel-Garcia wrote:
> > On Thu, Nov 29, 2018 at 10:31 PM 钱海远(Nathan)
> > wrote:
> >> We want to develop a feature like git pull request .
> >> [...]
> >
> > This seems infeasible. The working copy in which the merges would occur
> > d
On Fri, Nov 30, 2018 at 4:56 AM Julian Foad wrote:
> 钱海远(Nathan) wrote:
> > We want to develop a feature like git pull request .
>
> Some other companies are also interested in developing the same.
>
> There are a few different possible directions.
>
> You could implement pull requests (PR) using
Nico Kadel-Garcia wrote:
> On Thu, Nov 29, 2018 at 10:31 PM 钱海远(Nathan)
> wrote:
>> We want to develop a feature like git pull request .
>> [...]
>
> This seems infeasible. The working copy in which the merges would occur does
> not exist in the Subversion workflow.
Hello Nico! What do you m
On Thu, Nov 29, 2018 at 10:31 PM 钱海远(Nathan)
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.
>
Johan Corveleyn wrote on 2018-10-16:
> On Tue, Oct 16, 2018 at 11:56 AM 钱海远(Nathan)
> wrote:
>> During I am testing the -include' and '-exclude' options on 'svnadmin dump'
>> , I found
>> that if I copy a non-include file, the dump result is to add a file with
>> file content;
>> But if the
钱海远(Nathan) wrote:
> 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 rev
