Mvesteri tck tests2

Creating a MR to master from the branch created from 2016-patches doesn't really work. If you check the commits/changes, you see that you're merging a lot more than a couple of lines.

In any case, I don't think we need to keep the master up to date all the time. I can occasionally merge 2016-patches into master.

Bottom line -> no need to create MRs to master, unless you want to develop something for 2017.

Status changed to closed

Hi Rosen, Ah yes, of course, I see... My motivation to push also to the master is that the lhcb-head build is still OK, whereas the 2016-patches isn't. I guess that can be fixed today though? Mika

Ah yes, OK.