I second the advice to use git, unless you are working with a lot of
binary files.
On 01/11/17 14:38, Daniel Shahaf wrote:
> Eckard Klotz wrote on Tue, 31 Oct 2017 18:56 +0100:
>>> C:\Project...>*svnsync initialize https://.../p/moritz/Archive_SVN/
>>> file:///C:/Project/.../Archiev --disable-locking --allow-non-empty*
>>> /svnsync: E175008: While handling the 'svn:sync-from-url' property on
>>> '/p/moritz/Archive_SVN/!svn/bln/0'://
>>> //svnsync: E175008: Repository has not been enabled to accept revision
>>> propchanges;//
>>> //ask the administrator to create a pre-revprop-change hook/
>>>
>>> C:\Project...>rem svnsync synchronize DEST_URL [SOURCE_URL]
>>>
>>> C:\Project...>*svnsync synchronize https://.../p/moritz/Archive_SVN/
>>> file:///C:/Project.../Archiev --disable-locking*
>>> /svnsync: E000022: Destination repository has not been initialized/
>>>
>>> C:\Project...>pause
>>> Drücken Sie eine beliebige Taste . . .
>> I thing now I have as additional problem to set up the hook at
>> sourceforge. What do you think about?
> Ask sourceforge to enable the pre-revprop-change hook or use --disable-
> locking. In the latter case you have to ensure that no two instances
> of svnsync run concurrently, and additionally, svn:author & svn:date
> would not be set correctly. (Other revision properties are set as part
> of the commit, but these two are changed by svnsync using the revprop
> change API.)
Received on 2017-11-01 23:06:29 CET