Re: Adding new Subversion-private API's in patch releaqses

2011-02-14 Thread Greg Stein
On Mon, Feb 14, 2011 at 12:30, Stefan Sperling wrote: > On Mon, Feb 14, 2011 at 06:44:21PM +0200, Daniel Shahaf wrote: >> The 1.6.x-svn_fs_commit_txn branch adds a new Subversion-private API. >> >> On the one hand, if we add a new private API to 1.6.16, then clients >> compiled against 1.6.16 will

Re: Adding new Subversion-private API's in patch releaqses

2011-02-14 Thread Stefan Sperling
On Mon, Feb 14, 2011 at 06:44:21PM +0200, Daniel Shahaf wrote: > The 1.6.x-svn_fs_commit_txn branch adds a new Subversion-private API. > > On the one hand, if we add a new private API to 1.6.16, then clients > compiled against 1.6.16 will fail if run with 1.6.15 present in runtime. > (svn_ver_comp

Re: Adding new Subversion-private API's in patch releaqses

2011-02-14 Thread Daniel Shahaf
Consensus on IRC: all Subversion components should be upgraded/downgraded together, i.e., mod_dav_svn 1.6.16 with libsvn_repos 1.6.15 is "don't do that".

Adding new Subversion-private API's in patch releaqses

2011-02-14 Thread Daniel Shahaf
The 1.6.x-svn_fs_commit_txn branch adds a new Subversion-private API. On the one hand, if we add a new private API to 1.6.16, then clients compiled against 1.6.16 will fail if run with 1.6.15 present in runtime. (svn_ver_compatible() doesn't compare the patch number, only the major/minor numbers.)