Hi Philip,
sorry for the late reply. Thanks for your details.
That helped and works fine for us.
Kind regards
- Jan
Am 16.08.2013 11:51, schrieb Philip Martin:
> Jan Stürtz writes:
>
>> Hi list,
>> we have a quite old & grown svn repository here. With some "interesting"
>> svn:mergeinfo Pro
Note that it is sometimes much, much faster and creates much smaller and
cleaner repositories, to simply "svn export" and "svn import" the data
files themselves to a new repository. You don't get the history, but a
pointer to the old repository kept online in read only mode may be
considered enou
On Fri, Aug 16, 2013 at 10:51:58AM +0100, Philip Martin wrote:
> The mergeinfo is only parsed for partial dumps, i.e. when the start
> revision greater than one, as this allows the dump process to issue a
> warning when the mergeinfo refers to revisions not in the dump file.
> The only workaround i
Jan Stürtz writes:
> Hi list,
> we have a quite old & grown svn repository here. With some "interesting"
> svn:mergeinfo Properties. (see the diff below)
>
> This seems to be been allowed in earlier svn versions.
>
> For backup Issues svn copy worked fine for all the time,
> but now we want to up
Hi list,
we have a quite old & grown svn repository here. With some "interesting"
svn:mergeinfo Properties. (see the diff below)
This seems to be been allowed in earlier svn versions.
For backup Issues svn copy worked fine for all the time,
but now we want to update our server (svn version & hard
