On Mon, Jun 24, 2019 at 04:24:46PM +0200, Branko Čibej wrote: > 3. "This protocol is too chatty, let's invent a better one" > > Our wire protocol is a module. We can invent new ones without affecting > existing ones. Likewise for repository storage, or working copy storage, > etc. (with the latter actually being the hardest to change, due to > hysterical ... um, I mean historical reasons). >
Case in point: The ra-git branch started out as a repository access module, and later evolved into a repository fliesystem backend. Our design is flexible enough to allow for such features to be added. Even something like 'Git-backed SVN' would not require a 2.x branch. I would encourage new developers who want to work towards SVN 2.0 to gain some experience by finishing the ra-git branch and making a new 1.x release with built-in Git compatibility. This would go a long way towards allowing users to benefit from the advantages of both SVN and Git. Many environments run a mix of SVN and Git today and SVN will hopefully stay relevant for a longer period of time if it co-operates. Another useful feature would be built-in support for Git's fast-export streams in svnadmin dump/load. Git already has a reasonable level of SVN compatibility on their side. Such compatibility being a one-way street is not nice for users of either tool.
