Re: Display outstanding backported fixes for each release?

Julian Foad wrote on Thu, Jan 03, 2019 at 17:15:16 +0000:
> Julian Foad wrote:
> > [...] either inline or links to the verbose text samples above. [...]
>
> More precisely: I propose the output of "svn log" as illustrated in those
> samples,

Here you go.

[[[
% ./upcoming.py | tail -46
------------------------------------------------------------------------
r1847610 | svn-role | 2018-11-28 04:00:29 +0000 (Wed, 28 Nov 2018)

Merge the r1847181 group from trunk:

 * r1847181, r1847182, r1847188, r1847264
   Fix issue SVN-4792: Foreign repo copy of file adding mergeinfo.
   Justification:
     We don't want bogus mergeinfo.
   Votes:
     +1: julianfoad, brane, rhuijben
------------------------------------------------------------------------
r1849266 | svn-role | 2018-12-19 04:00:55 +0000 (Wed, 19 Dec 2018)

Merge the r1847572 group from trunk:

 * r1847572, r1847596
   fsfs: Fix SVN-4791, an issue with the DAG open_path() that was causing
   unexpected SVN_ERR_FS_NOT_DIRECTORY errors when attempting to open a path
   with `open_path_node_only | open_path_allow_null` flags.
   Justification:
     Some valid FSFS read operations errored out. This could break some
     end-user operations like 'update'.
   Votes:
     +1: julianfoad, brane, stefan2
------------------------------------------------------------------------
]]]

> concatenated with the full content of the relevant 'STATUS' file.

Minus the "Veto-blocked" changes, though.

Cheers,

Daniel