svn-r...@apache.org wrote on Sat, 03 Aug 2019 04:15 +00:00: > * upcoming.part.html: Automatically regenerated > > +++ subversion/site/publish/upcoming.part.html Sat Aug 3 04:15:02 2019 > @@ -2,113 +2,6 @@ > <pre style="border-style: none"> > Changes in ^/subversion/branches/1.12.x: > > ------------------------------------------------------------------------ > -<a href="https://svn.apache.org/r1860377";>r1860377</a> | svn-role | > 2019-05-30 04:00:08 +0000 (Thu, 30 May 2019) | 11 lines ... > ------------------------------------------------------------------------- > </pre> > > <p>Further changes currently under consideration are listed in each release > line's
This removed all the lines that the previous commit had added, except for the last diff context line. This is because the behaviour of upcoming.py depends on whether or not its cwd is the root of a stable branch source tree. The previous commit, r1864265, used ~/src/svn/site/ as the source tree; this commit used ~/src/svn/1.12.x/ as the source tree. The point where the two runs diverged would be tools/upcoming.py:get_reference_version(). Either way, the next time anything is merged to 1.12.x, upcoming.part.html should be auto-updated. Cheers, Daniel
