From: Adam Dinwoodie <adam@dinwoodie.org>
To: Erik Cervin Edin <erik@cervined.in>
Cc: Git Mailing List <git@vger.kernel.org>, Patrick Steinhardt <ps@pks.im>
Subject: Re: Bug using `fetch` with blank `-c` arguments to git
Date: Tue, 4 Jan 2022 16:15:25 +0000 [thread overview]
Message-ID: <CA+kUOakd0HaPk7PGh+4L6753KnsVaykczy31=5vrG91iJkcOfw@mail.gmail.com> (raw)
In-Reply-To: <CA+JQ7M_tOu5ahQSPZk5Be10rY_NDOmqLWj9b1On=KW8Rq2mk2w@mail.gmail.com>
On Tue, 4 Jan 2022 at 15:35, Erik Cervin Edin <erik@cervined.in> wrote:
>
> Minor clarifications
>
> On Tue, Jan 4, 2022 at 3:48 PM Adam Dinwoodie <adam@dinwoodie.org> wrote:
> >
> > While investigating some issues with a different project, I discovered
> > the command `git -c config.helper= fetch` was working with the Debian
> > ...
> > I see the same behaviour with `-c config.helper=`, `-c
> typos for "credential.helper" ?
"credential.helper" was certainly what I'd intended, but I see the
same behaviour with both options.
(I'd initially thought this was specifically due to the blank
argument, hence the email subject which I clearly failed to update,
but it looks like the issue occurs when using `-c` to set a config
option regardless of the option being set.)
> > Notably the behaviour does not affect all other git commands; `git -c
> > core.autocrlf= log -1` works as expected.
> You've only seen this with "git fetch"?
I've not tried to do any exhaustive testing, but I see this behaviour
with "git fetch", "git pull", "git bisect" and "git submodule"; I see
things apparently working as expected "git blame", "git commit", "git
push", "git reset", "git switch" and "git log".
next prev parent reply other threads:[~2022-01-04 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:36 Bug using `fetch` with blank `-c` arguments to git Adam Dinwoodie
2022-01-04 15:35 ` Erik Cervin Edin
2022-01-04 16:15 ` Adam Dinwoodie [this message]
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+kUOakd0HaPk7PGh+4L6753KnsVaykczy31=5vrG91iJkcOfw@mail.gmail.com' \
--to=adam@dinwoodie.org \
--cc=erik@cervined.in \
--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).