25 Sep
2017
25 Sep
'17
4:27 p.m.
On 25 September 2017 at 14:32, Neil Groves via Boost
Since this was not isolated to a single library, I assume this is quite easily done by mistake with common workflows. Perhaps we ought to consider having an automated test for .hpp (and other) files not being executable somewhere as a quality gate before subsequent releases?
It looks like it dates back to subversion, so I think it's unlikely to happen now.