I am using git-svn on top of the standard version Subversion repository.
Since we started using branches, git svn rebase became slow as hell (especially on Windows machines), and reports tons of the following warnings:
[...] W:unknown path/rev in svn:mergeinfo dirprop: /branches/2.0.x:3152 W:unknown path/rev in svn:mergeinfo dirprop: /branches/2.0.x:3157 W:unknown path/rev in svn:mergeinfo dirprop: /branches/2.0.x:3159-3196 [...] W:svn cherry-pick ignored (/branches/2.0.x:852-853,855-861,865-884,3078,3081-3082,3102,3105-3109,3111,3119,3121,3125-3126,3129,3131,3133-3135,3138,3143-3144,3146-3147,3150,3152,3157,3159-3196,3198-3201,3208-3219) - missing 1 commit(s) (eg 606cd9303f245a6c93cea57ecf4d6faf585616cf) r3222 = 240a0faa016ce74d708832a1d88e32b5f939bfb5 (refs/remotes/trunk)
What are all of them (unknown path / turnover and lack of commits) and how can I resolve them to avoid slowing down synchronization with the subversion repository?
We really stick to the standard Subversion repository layout and merge carefully with the branches. Thus, the properties of svn:mergeinfo are correct, and all this makes sense.
PS: I noticed that using git svn fetch at least seems to minimize warnings about the unknown path. But what are these βmissingβ warnings?