From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>,
git-packagers@googlegroups.com,
Stefan Beller <sbeller@google.com>, Jeff King <peff@peff.net>
Subject: Re: [ANNOUNCE] Git v2.20.0-rc2
Date: Tue, 04 Dec 2018 20:39:05 +0100 [thread overview]
Message-ID: <87in09ytd2.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq36rhjnts.fsf@gitster-ct.c.googlers.com>
On Sat, Dec 01 2018, Junio C Hamano wrote:
> * "git ls-remote $there foo" was broken by recent update for the
> protocol v2 and stopped showing refs that match 'foo' that are not
> refs/{heads,tags}/foo, which has been fixed.
> (merge 6a139cdd74 jk/proto-v2-ref-prefix-fix later to maint).
I started bisecting this thinking it was a regression, but found that
the reason the instructions in the protocol v2 announcement[1] don't
work anymore is because of it was due to 631f0f8c4b ("ls-remote: do not
send ref prefixes for patterns", 2018-10-31).
Perhaps we should note this more prominently, and since Brandon isn't at
Google anymore can some of you working there edit this post? It's the
first Google result for "git protocol v2", so it's going to be quite
confusing for people if after 2.20 the instructions in it no longer
work.
1. https://opensource.googleblog.com/2018/05/introducing-git-protocol-version-2.html
next prev parent reply other threads:[~2018-12-04 19:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 14:58 [ANNOUNCE] Git v2.20.0-rc2 Junio C Hamano
2018-12-03 20:21 ` [PATCH 0/3] " Martin Ågren
2018-12-03 20:21 ` [PATCH 1/3] RelNotes 2.20: move some items between sections Martin Ågren
2018-12-04 2:23 ` Junio C Hamano
2018-12-04 5:43 ` Martin Ågren
2018-12-04 5:43 ` [PATCH v2 " Martin Ågren
2018-12-04 5:43 ` [PATCH v2 2/3] RelNotes 2.20: clarify sentence Martin Ågren
2018-12-04 5:43 ` [PATCH v2 3/3] RelNotes 2.20: drop spurious double quote Martin Ågren
2018-12-03 20:21 ` [PATCH 2/3] RelNotes 2.20: clarify sentence Martin Ågren
2018-12-04 2:23 ` Junio C Hamano
2018-12-03 20:21 ` [PATCH 3/3] RelNotes 2.20: drop spurious double quote Martin Ågren
2018-12-04 2:26 ` Junio C Hamano
2018-12-03 20:45 ` [ANNOUNCE] Git v2.20.0-rc2 Johannes Schindelin
2018-12-04 19:39 ` Ævar Arnfjörð Bjarmason [this message]
2018-12-05 2:48 ` Stefan Beller
2018-12-05 4:05 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in09ytd2.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peff@peff.net \
--cc=sbeller@google.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.