From: Jonathan Nieder <jrnieder@gmail.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
git@vger.kernel.org, Derrick Stolee <dstolee@microsoft.com>,
bwilliams.eng@gmail.com
Subject: Re: connect: don't request v2 when pushing (Re: Protocol v2 in v2.27)
Date: Wed, 20 May 2020 19:45:58 -0700 [thread overview]
Message-ID: <20200521024558.GA102425@google.com> (raw)
In-Reply-To: <20200521023554.GE20332@Carlos-MBP>
Hi,
Carlo Marcelo Arenas Belón wrote:
> Sorry to hijack the thread, but hopefully this is not completely offtopic
> either, regarding v2 support.
Changing subject line.
> Is 1aa8dded3a (connect: don't request v2 when pushing, 2018-03-15) still
> relevant?
Can you elaborate a bit? Are you asking whether we should revert that
patch for git 2.28? Protocol v2 for push still does not exist, but we
have plans to introduce it soon (reusing more code from v0 push, so
this would hopefully have fewer teething pains than v2 for fetch).
Thanks,
Jonathan
next prev parent reply other threads:[~2020-05-21 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 19:17 [ANNOUNCE] Git v2.27.0-rc1 Junio C Hamano
2020-05-20 19:31 ` Jeff King
2020-05-20 20:02 ` Junio C Hamano
2020-05-20 20:31 ` Re* " Junio C Hamano
2020-05-20 21:24 ` Jeff King
2020-05-20 22:00 ` Protocol v2 in v2.27 (Re: Re* [ANNOUNCE] Git v2.27.0-rc1) Jonathan Nieder
2020-05-20 23:59 ` Junio C Hamano
2020-05-21 0:29 ` Jeff King
2020-05-21 2:15 ` Jonathan Nieder
2020-05-21 2:35 ` Carlo Marcelo Arenas Belón
2020-05-21 2:45 ` Jonathan Nieder [this message]
2020-05-21 3:26 ` connect: don't request v2 when pushing (Re: Protocol v2 in v2.27) Carlo Marcelo Arenas Belón
2020-05-21 11:54 ` Protocol v2 in v2.27 (Re: Re* [ANNOUNCE] Git v2.27.0-rc1) Derrick Stolee
2020-05-21 16:42 ` Junio C Hamano
2020-05-21 16:34 ` Junio C Hamano
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=20200521024558.GA102425@google.com \
--to=jrnieder@gmail.com \
--cc=bwilliams.eng@gmail.com \
--cc=carenas@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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 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 NNTP newsgroup(s).