mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Wu, Zhichen" <>
To: "" <>
Subject: Question About Git V2 Protocol & SHA256
Date: Tue, 29 Sep 2020 01:17:59 +0000	[thread overview]
Message-ID: <> (raw)

Hi Git Community,
Hope this email finds you well.
I’m Zhichen from AWS CodeCommit. I’m reaching out regarding 2 git features that we are planning for CodeCommit and your input would be critical for our next step.

1. Since v2 protocol has been launched for 2 years, is there any plan in the near future about v1 deprecation?
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?
Looking forward to hearing back from you.
Thanks in advance!
Zhichen Wu

             reply	other threads:[~2020-09-29  1:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  1:17 Wu, Zhichen [this message]
2020-09-29 22:13 ` Question About Git V2 Protocol & SHA256 Jeff King
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).