From: Daniele Sassoli <danielesassoli@gmail.com>
To: git@vger.kernel.org
Subject: Re: My summary of the Git Contributors' Summit 2026, was Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08)
Date: Tue, 10 Nov 2026 12:09:24 -0800 [thread overview]
Message-ID: <6572a59d-e2d2-4930-bc32-add248529d48@gmail.com> (raw)
In-Reply-To: <xmqqjymkqx9i.fsf@gitster.g>
On 10/11/2026 11:52, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Luca Milanesio <luca.milanesio@gmail.com> writes:
>>
>> [Administrivia: PLEASE TRIM YOUR QUOTES. Most parts of what you
>> quoted from the long message are irrelevant and did not help giving
>> context to your comments below].
>>
>>>> SHA-256 support across the ecosystem had been a blocker. GitHub reported
>>>> experimental support, with general availability expected around November.
>>>> GitLab already had public, non-experimental support, and libgit2 supports
>>>> it, too. JGit remains a gap; Google was not planning to fund that work.
>>> It looks like the above statement needs amending, see:
>>> https://gus26.gerritforge.com/schedule.html
>>>
>>> Google will present their plans for SHA-256 at the forthcoming Gerrit User Summit
>>> and jj Mini-Summit at the Google Campus in Sunnyvale CA.
>>>
>>> The talk is at 2:00 PM PDT: "SHA-256 in JGit: Why, What, and When (Xing Huang - Google)”
>>>
>>> Anyone joining from the Git community?
>> You forgot to mention that the talk is scheduled for Tuesday,
>> November 10th.
> And then we no longer see that talk on the Schedule page anymore.
> Sigh...
Yes, unfortunately the speaker's had a last minute family emergency and
couldn't make it
to the conference nor present remotely.
It's unfortunate that this happened, but we'll try to have this
presented at other follow-up
events very soon.
next prev parent reply other threads:[~2026-11-10 20:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 0:11 What's cooking in git.git (Sep 2026, #08) Junio C Hamano
2026-09-22 8:11 ` kh/format-patch-range-diff-notes Kristoffer Haugsbakk
2026-09-22 13:25 ` Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08) Johannes Schindelin
2026-09-22 13:49 ` Junio C Hamano
2026-09-22 17:06 ` Johannes Schindelin
2026-09-24 3:56 ` Junio C Hamano
2026-09-24 4:30 ` Junio C Hamano
2026-09-24 12:29 ` Johannes Schindelin
2026-09-24 17:00 ` Junio C Hamano
2026-09-24 18:08 ` Ramsay Jones
2026-09-22 18:44 ` My summary of the Git Contributors' Summit 2026, was " Johannes Schindelin
2026-09-23 11:55 ` Daniele Sassoli
2026-09-24 12:31 ` Johannes Schindelin
2026-09-25 9:53 ` Luca Milanesio
2026-09-23 12:52 ` D. Ben Knoble
2026-09-23 14:22 ` Security mailing list & process, was Re: My summary of the Git Contributors' Summit 2026 Toon Claes
2026-09-24 12:38 ` Johannes Schindelin
2026-09-23 14:40 ` Git Contributor' summit: Documentation, was: Re: My summary of the Git Contributors' Summit 2026, was Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08) Toon Claes
2026-09-23 15:15 ` Git Contributor' summit: Documentation, Junio C Hamano
2026-10-17 9:11 ` My summary of the Git Contributors' Summit 2026, was Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08) Luca Milanesio
2026-10-17 16:41 ` Junio C Hamano
2026-10-17 20:58 ` Luca Milanesio
2026-11-10 19:52 ` Junio C Hamano
2026-11-10 20:09 ` Daniele Sassoli [this message]
2026-11-10 20:47 ` Junio C Hamano
2026-10-19 5:38 ` Christian Couder
2026-10-19 5:43 ` Luca Milanesio
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=6572a59d-e2d2-4930-bc32-add248529d48@gmail.com \
--to=danielesassoli@gmail.com \
--cc=git@vger.kernel.org \
/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