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

Re: svn commit: r1845204 - in /subversion/trunk/subversion: mod_authz_svn/mod_authz_svn.c mod_dav_svn/mod_dav_svn.c

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 30 Oct 2018 21:03:53 +0000

Ruediger Pluem wrote on Tue, Oct 30, 2018 at 20:00:01 -0000:
>
>
> On 2018/10/30 18:09:42, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> > Branko Čibej wrote on Tue, 30 Oct 2018 10:22 +0100:
> > > It's important enough to be added to CHANGES, in the server-side
> > > bugfixes section, so please add a line there, for 1.12.0.
> >
> > Since we'll have to add this revision four times to CHANGES (on for each
> > of 1.9, 1.10, 1.11, 1.12), perhaps we should start using the CHANGES-in-log-
> > message convention a bit more? In this case, it would be something like
> > .
> > [U:server] mod_dav_svn, mod_authz_svn: Fix segfault under mod_http2 (SVN-4782)
> > .
>
> Should I add the above to the commit log? Or should I add an entry to CHANGES directly?
> I can do either way whatever you prefer.

In the log message please; release.py write-changelog will pick it from there
when we roll 1.12.0-alpha1.
Received on 2018-10-30 22:04:04 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.