mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: "Wu, Zhichen" <>
Cc: "brian m. carlson" <>,
	"" <>
Subject: Re: Question About Git V2 Protocol & SHA256
Date: Tue, 29 Sep 2020 18:13:11 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Sep 29, 2020 at 01:17:59AM +0000, Wu, Zhichen wrote:

> 1. Since v2 protocol has been launched for 2 years, is there any plan
>    in the near future about v1 deprecation?

I suppose it depends what you mean by deprecation.

v2 is not even the default yet (but hopefully will be soon, perhaps in
the next release).

Once that happens, I doubt that we will add new capabilities or features
to v1 in general. Old versions of Git would not be able to take
advantage of them anyway, and new ones would be using v2.

But I don't think v1 will go away for a long time. There will still be
v1 clients and v1 servers hanging around for many years, and modern
versions of Git will need to speak both.

> 2. I see v2 has a capability called “object-format” that provides SHA1
>    option. I’m wondering if that capability will be the only way for
>    client and server to start using SHA256? Or put it as another word,
>    will v2 protocol be the prerequisite of SHA256?

I think it would be impossible to handle object-format via v1, because
the v1 protocol writes the ref advertisement before any capabilities are
negotiated. So I think v1 must implicitly remain sha1-only (and a sha256
repository on the server side would need to either reject a v1 client,
or back-translate as it would for a v2 client which asks for sha1).


  reply	other threads:[~2020-09-29 22:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  1:17 Question About Git V2 Protocol & SHA256 Wu, Zhichen
2020-09-29 22:13 ` Jeff King [this message]
2020-09-29 22:41   ` Wu, Zhichen
2020-09-29 22:43   ` brian m. carlson
2020-09-29 23:07     ` Wu, Zhichen
2020-09-30  0:46     ` Jeff King
2020-09-30  2:19       ` brian m. carlson
2020-09-30 12:20         ` Jeff King
2020-10-01 23:52           ` brian m. carlson

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 \ \ \ \ \ \

* 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

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