At first I thought to provide special treatment to git config lines andotherwise keep raising uncaught exception, but then decided that it might bebetter to loose some progress information than to crash.Also _get_push_info below is doing similarish catching of all exceptions(although doesn't even log them).With this change, log (if enabled and not suppressed) would show[WARNING] Git informed while fetching: git config pull.rebase false  # merge (the default strategy)in the case of recently introduced change to the output in the followinggit commit :d18c950a69f3a24e1e3add3d9fc427641f53e12b is the first bad commitcommit d18c950a69f3a24e1e3add3d9fc427641f53e12bAuthor: Alex Henrie <alexhenrie24@gmail.com>Date:   Mon Mar 9 21:54:20 2020 -0600pull: warn if the user didn't say whether to rebase or to mergeOften novice Git users forget to say "pull --rebase" and end up with anunnecessary merge from upstream. What they usually want is either "pull--rebase" in the simpler cases, or "pull --ff-only" to update the copyof main integration branches, and rebase their work separately. Thepull.rebase configuration variable exists to help them in the simplercases, but there is no mechanism to make these users aware of it.Issue a warning message when no --[no-]rebase option from the commandline and no pull.rebase configuration variable is given. This willinconvenience those who never want to "pull --rebase", who haven't hadto do anything special, but the cost of the inconvenience is paid onlyonce per user, which should be a reasonable cost to help a number of newusers.Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>Signed-off-by: Junio C Hamano <gitster@pobox.com> builtin/pull.c               | 16 ++++++++++++++++ t/t5521-pull-options.sh      | 22 +++++++++++----------- t/t7601-merge-pull-config.sh | 38 ++++++++++++++++++++++++++++++++++++++ 3 files changed, 65 insertions(+), 11 deletions(-)Closesgitpython-developers#1014