apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: svn commit: r1308135 - in /apr/apr-util/branches/1.4.x: ./ CHANGES crypto/apr_crypto.c
Date Sun, 01 Apr 2012 21:03:06 GMT
On 01 Apr 2012, at 10:55 PM, Greg Stein wrote:

> -131 has no edit to CHANGES.
> When performing backports, you should commit *just* the backport. If
> you want to make other changes, then keep them in a separate commit.
> Combining changes like this is poor branch policy. It means that we
> can no longer trust that a backport is *JUST* the backport. We have to
> investigate to determine whether other changes were made in the
> commit.

I personally agree with you, but I lost that fight when the issue of CHANGES files was thrashed
out on this list.

I'm sure those who set the current CHANGES file policy will step forward at this point and
explain their reasoning behind it.


View raw message