Patrick Steinhardt <ps@xxxxxx> writes: >> Is setting it up as a command line config option the way you expect to >> use this, and if so why not make it a full blown command line option >> with the previous caveats that were discussed before? > > If you did this as a command-line option, you'd now be forced to add it > to every single command you want to support this: git-fetch, git-pull, > git-remote, git-ls-remote and maybe others I forgot about. On the other > hand, by having this as a configuration variable in `http.c` all of > those commands benefit the same. It is not an argument against the command line option that you find it more work to implement and cumbersome to plumb the information through the callgraph, though. Subcommands like "git commit" shouldn't have to know how host names are mapped to IP addresses, and teaching the option only to subcommands that the feature is relevant, and documenting the option in their manual pages, would make it much easier to discover and learn. > Overall, I think it is preferable to keep this as an option as opposed > to adding such an obscure parameter to all of the commands. I favor implementing this as a configuration that is primarily meant to be used from the command line (i.e. "git -c var=val"), ONLY BECAUSE the feature itself is not something that should be widely used (the users should futz with their DNS if they need something more permanent), and adding it as a configuration would be a more quick and dirty way that needs less developer resources now ;-) To purists, it may make more sense to add this feature and make it accessible only from the command line without matching configuration variable---that would enforce the assumed use case (i.e. only after another part of the system asked DNS, performed some check on the resulting IP address, and decided to ask Git to interact with that URL, use this mechanism to ensure Git interacts with that IP address that was vetted, to avoid TOCTOU mistakes) more clearly. I am personally open to such a purer counterproposal with working code ;-) >> I also think it might be a little confusing (and probably warranted of >> an advice message) if git will decide based on a configuration >> somewhere in its resolution tree that the IP I am connecting is >> different than the one I expect it to use through the system >> configured resolution mechanism for such a thing. > > That's true already though, isn't it? A user may set `url.*.insteadOf` > and be surprised at a later point that their URLs are getting redirected > somewhere else. And there's probably a lot more examples where a user > may be confused when forgetting about certain configuration variables > that change the way Git behaves. > > I also don't think that using an advise here would be ideal. The main > use case of this configuration variable is going to be servers, and > there is a high chance that they might actually be parsing output of any > such commands. Forcing them to always disable this advise doesn't feel > like the right thing to do. All correct. If the users set configuration variables, the fact that we honored their configuration variables settings and behaved accordingly is *NOT* an advise-worthy event. Thanks.
