list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Josep Torra <>
Subject: Possible regression in git 2.26.0
Date: Tue, 31 Mar 2020 19:13:25 +0200	[thread overview]
Message-ID: <> (raw)

Today I'd noticed a failure in some custom automation that seems to
came as a side effect after of a git client update.

The issue issue I'd spotted is the following:

$ git clone git://
Cloning into 'linux/bionic'...
fatal: remote error: Parameters must have values

Reverting to git 2.17.1 didn't show the issue.

I'd asked at #git in freenode and @rafasc was able to reproduce and
bisect, pointing to

For the time being I'd added `-c protocol.version=0` as a temporary workaround.

Is this a regression?

Thanks for looking into this.

Josep Torra

             reply	other threads:[~2020-03-31 17:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 17:13 Josep Torra [this message]
2020-03-31 17:22 ` Konstantin Ryabitsev
2020-04-10 21:00   ` Jeff King
2020-04-03 18:58 ` Jeff King
2020-04-03 19:36   ` Jeff King
2020-04-03 19:53     ` Junio C Hamano
2020-04-04 15:20       ` Jeff King
2020-04-07 14:52         ` Jeff King

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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 inbox:

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).