Comment 1 for bug 1356591

This was intentional behavior back when everyone had their sample configs in Git and changes were reviewed. Now that most (all?) projects aren't doing that, we could potentially stop sorting.

I don't know if that would fix this particular issue though. The reason we started sorting was that everything was being written in random order before, which meant adding one option could trigger a reorder of the entire file.