From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2024, #04; Wed, 12)
Date: Thu, 13 Jun 2024 07:52:13 +0200 [thread overview]
Message-ID: <ZmqJDVTAiBrYJGRW@tanuki> (raw)
In-Reply-To: <xmqqcyolofar.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
On Wed, Jun 12, 2024 at 05:30:04PM -0700, Junio C Hamano wrote:
> * ps/document-breaking-changes (2024-06-04) 4 commits
> - BreakingChanges: document that we do not plan to deprecate git-checkout
> - BreakingChanges: document removal of grafting
> - BreakingChanges: document upcoming change from "sha1" to "sha256"
> - docs: introduce document to announce breaking changes
>
> The structure of the document that records longer-term project
> decisions to deprecate/remove/update various behaviour has been
> outlined.
>
> Getting there.
> source: <cover.1717504292.git.ps@pks.im>
Just to make sure I understand the status: do you expect me to do
anything in this context? The latest version did have some final
discussion, but from my point of view there wasn't anything actionable.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-13 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 0:30 What's cooking in git.git (Jun 2024, #04; Wed, 12) Junio C Hamano
2024-06-13 5:52 ` Patrick Steinhardt [this message]
2024-06-13 15:22 ` Junio C Hamano
2024-06-14 5:52 ` Patrick Steinhardt
2024-06-13 13:35 ` Phillip Wood
2024-06-13 16:20 ` 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=ZmqJDVTAiBrYJGRW@tanuki \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.