Anton Shepelev wrote on Thu, 26 Mar 2020 01:10 +0300:
> Daniel Shahaf:
> > 2. We can't trace copies forward. If trunk had been renamed or
> > forked after the merge, a simplistic "Take the
> > copyfrom_path@copyfrom_rev, change the copyfrom_rev to 'HEAD',
> > and use that as the URL to merge
Daniel Shahaf:
> Stefan Sperling wrote on Wed, 25 Mar 2020 15:07 +0100:
> > On Wed, Mar 25, 2020 at 04:45:29PM +0300, Anton Shepelev wrote:
> > > Why does even the basic sync-merging require that the user
> > > specify the source URL, as in:
> > >
> > > svn merge ^/project/trunk
> > >
> > > I
Stefan Sperling wrote on Wed, 25 Mar 2020 15:07 +0100:
> On Wed, Mar 25, 2020 at 04:45:29PM +0300, Anton Shepelev wrote:
> > Hello, all
> >
> > Why does even the basic sync-merging require that the user
> > specify the source URL, as in:
> >
> > svn merge ^/project/trunk
> >
> > I think this
On Wed, Mar 25, 2020 at 04:45:29PM +0300, Anton Shepelev wrote:
> Hello, all
>
> Why does even the basic sync-merging require that the user
> specify the source URL, as in:
>
> svn merge ^/project/trunk
>
> I think this requirement is redundant because SVN know
> exactly from which original
Hello, all
Why does even the basic sync-merging require that the user
specify the source URL, as in:
svn merge ^/project/trunk
I think this requirement is redundant because SVN know
exactly from which original original directory the branch
was created by svn cp. Will you consider simplifying
