[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1864300 - /subversion/site/publish/upcoming.part.html

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sun, 04 Aug 2019 23:31:42 +0000

svn-role_at_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:
>
> ------------------------------------------------------------------------
> -r1860377 | 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
Received on 2019-08-05 01:31:57 CEST

This is an archived mail posted to the Subversion Dev mailing list.