> In order to realize any new feature that needs to read the existing > (i.e. per-machine or per-user) configuration files to affect the > behaviour of "git clone", whether it is the "give default to > --origin option" or any other thing, first needs to fix the start-up > sequence so that the configuration is read once before we process > command line options, which is the norm. Only after that is done, > we can build the clone.defaultRemoteName and other features that > would be affected by the settings of clone.* variables on top, and > it is not wise to mix the foundation with a new feature that uses > the foundation. Makes sense! Thanks for all your help -- I _really_ appreciate it. I'll give it a try over the next few days.
