I mean we could leave the current 1.8.x backport proposal unchanged. Alternatively, tweaking your patch to make the new API private for 1.8.x is fine; probably even better as it's likely to make future backports easier. On 22 May 2015 12:46 pm, "Philip Martin" <philip.mar...@wandisco.com> wrote:
> Branko Čibej <br...@wandisco.com> writes: > > > On 22.05.2015 10:50, Philip Martin wrote: > >> > >> Another approach would be to have a function to enable flushing directly > >> on the stream created by svn_stream_from_aprfile2() without creating a > >> new stream. This is probably the smallest/simplest patch. After > >> reverting r1680819: > > > > [...] > > > > Big +1! Let's do it this way. We can keep the 1.8.x backport unchanged, > too. > > Not sure what you mean by 1.8.x being unchanged. My patch has a new > public API and a 1.8.x backport would make it private, unless we make > the new API private everywhere. > > -- > Philip Martin | Subversion Committer > WANdisco // *Non-Stop Data* >
