From: Adam Dinwoodie <adam@dinwoodie.org>
To: Git Mailing List <git@vger.kernel.org>
Cc: Patrick Steinhardt <ps@pks.im>
Subject: Bug using `fetch` with blank `-c` arguments to git
Date: Tue, 4 Jan 2022 12:36:50 +0000 [thread overview]
Message-ID: <CA+kUOak9_RLpdr9d4pQiwU=K42taCwhMdg5WkLP4GreQd4yWig@mail.gmail.com> (raw)
While investigating some issues with a different project, I discovered
the command `git -c config.helper= fetch` was working with the Debian
stable version of Git (v2.30.2) but not with my local build
(v2.34.1.428.gdcc0cd074f).
Specifically, I see the following output:
$ ./git -c credential.helper= fetch
error: bogus format in GIT_CONFIG_PARAMETERS
fatal: unable to parse command-line config
Investigating with `git bisect`, the change in behaviour seems to have
been introduced in 1ff21c05ba ("config: store "git -c" variables using
more robust format", 2021-01-12).
I see the same behaviour with `-c config.helper=`, `-c
core.autocrlf=`, `-c core.autocrlf` and `-c core.autocrlf=true`..
Notably the behaviour does not affect all other git commands; `git -c
core.autocrlf= log -1` works as expected.
I think this is a regression; I can't see any reason why these
commands shouldn't work.
Curiously, I'm seeing this behaviour on both my Raspberry Pi OS and
Debian Bullseye systems, but not my Cygwin systems. I've not yet tried
to work out what the difference is there. In all cases, I was testing
with my own build, built with `make -j<num> configure && ./configure
--prefix=$HOME/.local && make -j<num>`.
next reply other threads:[~2022-01-04 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:36 Adam Dinwoodie [this message]
2022-01-04 15:35 ` Bug using `fetch` with blank `-c` arguments to git Erik Cervin Edin
2022-01-04 16:15 ` Adam Dinwoodie
2022-01-04 16:30 ` Erik Cervin Edin
2022-01-04 20:04 ` Bryan Turner
2022-01-04 21:00 ` Adam Dinwoodie
2022-01-06 10:11 ` Adam Dinwoodie
2022-01-07 12:52 ` Patrick Steinhardt
2022-01-07 13:04 ` Adam Dinwoodie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+kUOak9_RLpdr9d4pQiwU=K42taCwhMdg5WkLP4GreQd4yWig@mail.gmail.com' \
--to=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).