> I think this really is a bug in our runtime. The flag was invented > just for precaution, in case a module would rely on the no-copy > behaviour. That is really close to saying: we will not fix > any more bugs in 2.4.x as someone could rely on it.
I don't think this bit is fair. Every config section behaves the same -- modules get a new configuration when their directives are used in the section.
