Severe behavioural change regressions in release branch

Ben Boeckel ben.boeckel-5opLkZggLXlBDgjK7y7TUQ at
Sat Oct 25 00:23:42 BST 2014

On Sat, Oct 25, 2014 at 08:50:12 +1300, Ben Cooksley wrote:
> On Sat, Oct 25, 2014 at 5:44 AM, Stephen Kelly <steveire-Re5JQEeQqe8AvxtiuMwx3w at> wrote:
> > Is now using the release branch of cmake.git instead of the
> > next branch? When/why did that change?
> This was changed around about
> The motivation behind the change was to get the CI system to have the
> same setup as developers I think, and to avoid regressions in 3.1
> which had been causing some build problems at the time. Those same
> regressions are the ones causing us issues now.
> Interestingly, the commit which was identified as causing the issue
> occurred back in March, yet this thread was in June. So perhaps there
> may be other commits interacting here (or that was the time when the
> commit previously identified was merged into the next branch).

Earlier this year, I was working on lots of performance metrics of CMake
and this was part of it. There ended up being more than a dozen branches
resulting from that work (some of them still unmerged). Doing some
digging shows that this is where the commit finally hit master:

    commit bd20dd6b8a925a421167602027fff9b904fd0822
    Merge: b041fc1 e17a69b
    Author: Brad King <brad.king-5opLkZggLXlBDgjK7y7TUQ at>
    Date:   Thu Jun 12 11:28:44 2014 -0400

so June looks right.


Powered by

Please keep messages on-topic and check the CMake FAQ at:

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support:
CMake Consulting:
CMake Training Courses:

Visit other Kitware open-source projects at

Follow this link to subscribe/unsubscribe:

More information about the kde-core-devel mailing list