On Fri, Sep 30, 2011 at 8:00 PM, PR wrote:
> Hello,
>
> I had initially got a lot of great feedback from the group.
>
> I had decided to migrate the repo using the svnsync and the new server is
> 1.7 rc3 for the POC migration. (old server 1.4.6).
>
> Initially every thing was smooth now we are no
Daniel Shahaf wrote on Sat, Oct 01, 2011 at 09:06:33 +0300:
> If you think Subversion should promise a specific error code in this
> situation, please file a bug against svnsync.
I meant: file a bug after discussing it on this list, per the normal bug
filing guidelines. Thanks.
Konstantin Kolinko wrote on Sat, Oct 01, 2011 at 04:53:01 +0400:
> 2011/10/1 PR
> > svnsync: E22: Destination repository already contains revision history;
> > co
> > nsider using --allow-non-empty if the repository's revisions are known to
> > mirr
> > or their respective revisions in the s
On Fri, Sep 30, 2011 at 5:53 PM, Konstantin Kolinko
wrote:
> 2011/10/1 PR
> >
> > Hello,
> > I had initially got a lot of great feedback from the group.
> > I had decided to migrate the repo using the svnsync and the new server is
> 1.7 rc3 for the POC migration. (old server 1.4.6).
> > Initially
2011/10/1 PR
>
> Hello,
> I had initially got a lot of great feedback from the group.
> I had decided to migrate the repo using the svnsync and the new server is 1.7
> rc3 for the POC migration. (old server 1.4.6).
> Initially every thing was smooth now we are noticing that some repositories
> we
