Re: [1.8.0] make two-argument fetch update remote branches

Jay Soffian [off-list ref] writes:

Would it make sense to group the pre-1.8 compatibility switches
together in some way, if there will be several of them? Maybe

[compat]
   fetchUpdateRemoteNamespace = false
   ...

I don't think so.

If these configuration variables are expected to be removed in some
future, such a layout might make sense, but what is proposed is to default
them to a different behaviour from today at 1.8.0 boundary, and we are not
going to remove the ability to invoke the current behaviour with these
variables.  It would make it a lot easier to find and understand if the
variables are grouped by functionality like all the other regular
variables, as these new ones are after all regular ones.

Just thinking aloud, too.