On Wed, Jan 25, 2017 at 9:16 PM, Ryan Schmidt <subversion-2...@ryandesign.com> wrote: > >> On Jan 25, 2017, at 09:59, Dalton, Bill (GE Energy Connections) >> <bill.dal...@ge.com> wrote: >> >> We know how we would want it to work. I'm guessing that if we need it >> "fixed", that we would need to get the souce, make our fix, and build our >> own version? That has the advantage of giving us control on how it works >> for us, but makes updating to future versions complicated and risky. > > If you know how to fix a Subversion bug and contribute that fix, I'm sure the > Subversion developers would be appreciative. >
Yes, absolutely. And I think a solution is definitely possible, if someone is prepared to spend time on it. In this case, I think it's best to start from that discussion thread from 2015 [1], try to summarize where it stranded, and bring it up again on the d...@subversion.apache.org mailinglist with your view on how it should work. We can then try finding a consensus in the community on the specs. Apart from discussing how it should behave (which is the first step), you might want to take a look at Subversions Community Guide [2]. [1] http://svn.haxx.se/dev/archive-2015-08/0179.shtml [2] http://subversion.apache.org/docs/community-guide/ -- Johan
