From patchwork Fri Jun 14 06:42:34 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Patrick Steinhardt X-Patchwork-Id: 13697919 Received: from fhigh8-smtp.messagingengine.com (fhigh8-smtp.messagingengine.com [103.168.172.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EBD121474C4 for ; Fri, 14 Jun 2024 06:42:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=103.168.172.159 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347361; cv=none; b=fM0OKyogPVz/Ecf0rMhOTAhstuCoJcwSDIC9c/d9/359Q58Se9R+zL46Su2SOEecrST6h9Z/gvNUTLX7Sams80vOD/xgmqPDz4DsDaBPY2UEB8odav1P5I4giSUMuHd1YpJJcxEB+DZVKt33KFOtg8H6GifdkhZJxPgdTqfwp28= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347361; c=relaxed/simple; bh=yjRxY865Nl3opplYGojSJv2ah0ORmST4Qa23Q46kIq0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ikSyYtMSs62Ye0BB+eaO1N5TzKaEnUHsahj5rvfjXeKCQiA9XnWpzylq1s9s82B5aIERMucUsj0btSS3xcWI5qhAr/Vt9hk5S9OAqu4q6AUWLkQe0Ky4PDchu7o3Z5d33kG9jQF/j9Tiwlhnji5ELY48NGITIgI7H21dys3aKJA= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im; spf=pass smtp.mailfrom=pks.im; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b=GdM6TJsV; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=EviMjzwp; arc=none smtp.client-ip=103.168.172.159 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pks.im Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b="GdM6TJsV"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="EviMjzwp" Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.nyi.internal (Postfix) with ESMTP id D96871140218; Fri, 14 Jun 2024 02:42:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 14 Jun 2024 02:42:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pks.im; h=cc:cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1718347358; x=1718433758; bh=F/3bikShhj ITOiLZ+h4O+eed0BKRB3SboZPZ994f7AE=; b=GdM6TJsViIeKMfM3Gm3j2v+VTG eHyUBsdYd3nQ6PIck09+iuNdMJmUBO6aOzJGdmzwPVIDsFliVrPIv5GM0pLW7ReI T0XuiNgZFbZQ7++3kMvloSxOyh6lBVuCvS+im9ixZ3CBSQ24EnWAM1rhGjVkoFw1 ThBs9S7nQNTk9WW/vIKJBUqIGUxwhyv3bCW80tXWyHzPraTPI4XKu6ow0VHZH6xq io402iajX0yDK8kTf0l3E4OCwwIjux4VSAV8FwxUoUrSYz1JrHkR2DHVS+2MKRPg avCKIwOWgH5MW9OkIqFulzXNt3pBiGgEJpzzcYKZwBiskZ2vv0YLUCRDk4Rw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1718347358; x=1718433758; bh=F/3bikShhjITOiLZ+h4O+eed0BKR B3SboZPZ994f7AE=; b=EviMjzwprDJEAqlyglAR+z7jcOBPUbqrG6WetgppYvyp QE/JZJrbjbt84i6yxXbwlo/GVHYxIQ05h3dK8F/4R4QOSFjV78Yiupyjncx0sRbZ +zq2ffWPdfQ6vkWhjIjx5zekwM4pWLth6S+4MRxMuFDruL5+VlMf17G2v+lnz5F9 ri7neuXPTpZHT8l9Duxrxq03IRqr/Wls3plXm53JXQaRknsY5+nzrrE+fVhwXquS eGBhm8roGXid2OmnAxjn7TMhqXxIhFkTrtMbWh65Euc3da3eJFWrGLjMhVcEX+k+ bA7v2Rw9QphwM7+TNY3/j+h5pA4xYpoNUyJgD1hzlQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfedukedguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrrght rhhitghkucfuthgvihhnhhgrrhguthcuoehpshesphhkshdrihhmqeenucggtffrrghtth gvrhhnpeeiveektdfggfeluefgvdelvdeftdfhgeeugeefveejleeufeekgeefffehgfel gfenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepphhssehpkhhsrdhimh X-ME-Proxy: Feedback-ID: i197146af:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Jun 2024 02:42:37 -0400 (EDT) Received: by localhost (OpenSMTPD) with ESMTPSA id b6ce7653 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 14 Jun 2024 06:42:22 +0000 (UTC) Date: Fri, 14 Jun 2024 08:42:34 +0200 From: Patrick Steinhardt To: git@vger.kernel.org Cc: Johannes Schindelin , Phillip Wood , Justin Tobler , Junio C Hamano , Dragan Simic , Karthik Nayak , Todd Zullinger Subject: [PATCH v7 1/4] docs: introduce document to announce breaking changes Message-ID: <6348f27b591f306d79c69594ed3157e22ac4774c.1718345026.git.ps@pks.im> References: Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Over time, Git has grown quite a lot. With this evolution, many ideas that were sensible at the time they were introduced are not anymore and are thus considered to be deprecated. And while some deprecations may be noted in manpages, most of them are actually deprecated in the "hive mind" of the Git community, only. Introduce a new document that tracks such breaking changes, but also deprecations which we are not willing to go through with, to address this issue. This document serves multiple purposes: - It is a way to facilitate discussion around proposed deprecations. - It allows users to learn about deprecations and speak up in case they have good reasons why a certain feature should not be deprecated. - It states intent and documents where the Git project wants to go, both in the case where we want to deprecate, but also in the case where we don't want to deprecate a specific feature. The document is _not_ intended to cast every single discussion into stone. It is supposed to be a living document that may change over time when there are good reasons for it to change. Signed-off-by: Patrick Steinhardt --- Documentation/BreakingChanges.txt | 80 +++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 Documentation/BreakingChanges.txt diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt new file mode 100644 index 0000000000..cb7e30312f --- /dev/null +++ b/Documentation/BreakingChanges.txt @@ -0,0 +1,80 @@ += Upcoming breaking changes + +The Git project aims to ensure backwards compatibility to the best extent +possible. Minor releases will not break backwards compatibility unless there is +a very strong reason to do so, like for example a security vulnerability. + +Regardless of that, due to the age of the Git project, it is only natural to +accumulate a backlog of backwards-incompatible changes that will eventually be +required to keep the project aligned with a changing world. These changes fall +into several categories: + +* Changes to long established defaults. +* Concepts that have been replaced with a superior design. +* Concepts, commands, configuration or options that have been lacking in major + ways and that cannot be fixed and which will thus be removed without any + replacement. + +Explicitly not included in this list are fixes to minor bugs that may cause a +change in user-visible behavior. + +The Git project irregularly releases breaking versions that deliberately break +backwards compatibility with older versions. This is done to ensure that Git +remains relevant, safe and maintainable going forward. The release cadence of +breaking versions is typically measured in multiple years. We had the following +major breaking releases in the past: + +* Git 1.6.0, released in August 2008. +* Git 2.0, released in May 2014. + +We use . release numbers these days, starting from Git 2.0. For +future releases, our plan is to increment in the release number when we +make the next breaking release. Before Git 2.0, the release numbers were +1.. with the intention to increment for "usual" breaking +releases, reserving the jump to Git 2.0 for really large backward-compatibility +breaking changes. + +The intent of this document is to track upcoming deprecations for future +breaking releases. Furthermore, this document also tracks what will _not_ be +deprecated. This is done such that the outcome of discussions document both +when the discussion favors deprecation, but also when it rejects a deprecation. + +Items should have a clear summary of the reasons why we do or do not want to +make the described change that can be easily understood without having to read +the mailing list discussions. If there are alternatives to the changed feature, +those alternatives should be pointed out to our users. + +All items should be accompanied by references to relevant mailing list threads +where the deprecation was discussed. These references use message-IDs, which +can visited via + + https://lore.kernel.org/git/$message_id/ + +to see the message and its surrounding discussion. Such a reference is there to +make it easier for you to find how the project reached concensus on the +described item back then. + +This is a living document as the environment surrounding the project changes +over time. If circumstances change, an earlier decision to deprecate or change +something may need to be revisited from time to time. So do not take items on +this list to mean "it is settled, do not waste our time bringing it up again". + +== Git 3.0 + +The following subsections document upcoming breaking changes for Git 3.0. There +is no planned release date for this breaking version yet. + +Proposed changes and removals only include items which are "ready" to be done. +In other words, this is not supposed to be a wishlist of features that should +be changed to or replaced in case the alternative was implemented already. + +=== Changes + +=== Removals + +== Superseded features that will not be deprecated + +Some features have gained newer replacements that aim to improve the design in +certain ways. The fact that there is a replacement does not automatically mean +that the old way of doing things will eventually be removed. This section tracks +those features with newer alternatives. From patchwork Fri Jun 14 06:42:39 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Patrick Steinhardt X-Patchwork-Id: 13697920 Received: from fhigh8-smtp.messagingengine.com (fhigh8-smtp.messagingengine.com [103.168.172.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8A1D81474C4 for ; Fri, 14 Jun 2024 06:42:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=103.168.172.159 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347366; cv=none; b=U/QTI7DzvJnwmwLJRIrBzhKpFsHL4Ipfx+nzWU10woKprrlxXi/+SPJPxz2piaZWx1HquhbYf1x95vdS2FJkOLCAsQL+I5NN3BTtN3M9zZ70WKokun4PibrxPAZgCwRtPZgvyyRKVqNOyT20zGGL7SnAEzFQfHfHJecEewRNCxY= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347366; c=relaxed/simple; bh=LOfVoy6doLAahEFcvTQJFxRcSZkV2+QoE03CoGIOVgw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=hnrOOQOURZWoUBt5eeNYYkkKbYYEVl4duZrtVEAHaGF2BhlUc+uNuxbodm/HXznDuhcXgCfJxcAWqG/1Y57K3ild8nHmbn3VgqwcBhsKYmuy5WsvLh6/L2LxZqc++q2o9O+CPxipozITaDpJ4ljTMzmwZV9cfwcDCZZ62hKJoC8= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im; spf=pass smtp.mailfrom=pks.im; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b=EQp1bspg; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=iheYLqGY; arc=none smtp.client-ip=103.168.172.159 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pks.im Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b="EQp1bspg"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="iheYLqGY" Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 92B35114021A; Fri, 14 Jun 2024 02:42:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 14 Jun 2024 02:42:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pks.im; h=cc:cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1718347363; x=1718433763; bh=3ElLNi3yT0 xR3rB97C21WF7wJ2CoZVU61SsOlk49X0Q=; b=EQp1bspgcypVnxpL+HAPS/i/se CJu3yghF5++FifVUayqcvYP6ayTELqEQhUwBO52vfq+MXBUMe2OjXEBnNkRzgYKa api9whVN8/MQCXTbkhWtEIx/OVhI+XBcBLvdQrEofawdDku5eXlFGuNAmXrDizpj UxFX6WWliRPpZvZJZDWJwEtRfBZJ8KOlrfQ9VoInKbahwKhltlYFkCxb+j6w8elA VstCw2f3foSuo0Kk0mvgHn/Ss4nNHiZAKTGD6SQaDOE8TRsX1DIxWIqluCTy/Kao uweUMQIgGDIpnlzVN0YJHrt+TmtTdRqFy2L+xShJGuGP2b8rzAjy33PTqQGQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1718347363; x=1718433763; bh=3ElLNi3yT0xR3rB97C21WF7wJ2Co ZVU61SsOlk49X0Q=; b=iheYLqGYTUiLXA/xqRvC8W0c35MbNG5emr9BEJget/WV Q3NWT4rtwD9aiIqmixaZSJB7KaHeJmloGuTzysXnFXx7+iMNnb0MDUCOX+nxDug7 Lmymm9ZjbIphBcsJ+4mrEZjl/pRfbop02oAbox8jWWYklG2FtfhFtL0DWT4sf+Ce T5medn8iqUL1E7ApHGPyfKd0KC+nmtB+DEbbZd+8LLJpHL03cPUpGzS4+Fk8PQH5 7WMansSo6cWaKHn2JrNBAai7ANQd0P3P6pyQm8pyF8GPjPWSbH7cLCSdbRjhwKtB +ANk+x+fTuNoQgU4lzgaPjul/0ZQRq5l2c8kWnfN5Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfedukedguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrrght rhhitghkucfuthgvihhnhhgrrhguthcuoehpshesphhkshdrihhmqeenucggtffrrghtth gvrhhnpeeukedtvedtffevleejtefgheehieegkeeluddvfeefgeehgfeltddtheejleff teenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpsh esphhkshdrihhm X-ME-Proxy: Feedback-ID: i197146af:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Jun 2024 02:42:42 -0400 (EDT) Received: by localhost (OpenSMTPD) with ESMTPSA id a49c0d06 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 14 Jun 2024 06:42:26 +0000 (UTC) Date: Fri, 14 Jun 2024 08:42:39 +0200 From: Patrick Steinhardt To: git@vger.kernel.org Cc: Johannes Schindelin , Phillip Wood , Justin Tobler , Junio C Hamano , Dragan Simic , Karthik Nayak , Todd Zullinger Subject: [PATCH v7 2/4] BreakingChanges: document upcoming change from "sha1" to "sha256" Message-ID: References: Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Starting with 8e42eb0e9a (doc: sha256 is no longer experimental, 2023-07-31), the "sha256" object format is no longer considered to be experimental. Furthermore, the SHA-1 hash function is actively recommended against by for example NIST and FIPS 140-2, and attacks against it are becoming more practical both due to new weaknesses (SHAppening, SHAttered, Shambles) and due to the ever-increasing computing power. It is only a matter of time before it can be considered to be broken completely. Let's plan for this event by being active instead of waiting for it to happend and announce that the default object format is going to change from "sha1" to "sha256" with Git 3.0. All major Git implementations (libgit2, JGit, go-git) support the "sha256" object format and are thus prepared for this change. The most important missing piece in the puzzle is support in forges. But while GitLab recently gained experimental support for the "sha256" object format though, to the best of my knowledge GitHub doesn't support it yet. Ideally, announcing this upcoming change will encourage forges to start building that support. Signed-off-by: Patrick Steinhardt --- Documentation/BreakingChanges.txt | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt index cb7e30312f..68ad42d805 100644 --- a/Documentation/BreakingChanges.txt +++ b/Documentation/BreakingChanges.txt @@ -70,6 +70,36 @@ be changed to or replaced in case the alternative was implemented already. === Changes +* The default hash function for new repositories will be changed from "sha1" + to "sha256". SHA-1 has been deprecated by NIST in 2011 and is nowadays + recommended against in FIPS 140-2 and similar certifications. Furthermore, + there are practical attacks on SHA-1 that weaken its cryptographic properties: ++ + ** The SHAppening (2015). The first demonstration of a practical attack + against SHA-1 with 2^57 operations. + ** SHAttered (2017). Generation of two valid PDF files with 2^63 operations. + ** Birthday-Near-Collision (2019). This attack allows for chosen prefix + attacks with 2^68 operations. + ** Shambles (2020). This attack allows for chosen prefix attacks with 2^63 + operations. ++ +While we have protections in place against known attacks, it is expected +that more attacks against SHA-1 will be found by future research. Paired +with the ever-growing capability of hardware, it is only a matter of time +before SHA-1 will be considered broken completely. We want to be prepared +and will thus change the default hash algorithm to "sha256" for newly +initialized repositories. ++ +An important requirement for this change is that the ecosystem is ready to +support the "sha256" object format. This includes popular Git libraries, +applications and forges. ++ +There is no plan to deprecate the "sha1" object format at this point in time. ++ +Cf. <2f5de416-04ba-c23d-1e0b-83bb655829a7@zombino.com>, +<20170223155046.e7nxivfwqqoprsqj@LykOS.localdomain>, +. + === Removals == Superseded features that will not be deprecated From patchwork Fri Jun 14 06:42:44 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Patrick Steinhardt X-Patchwork-Id: 13697921 Received: from fhigh8-smtp.messagingengine.com (fhigh8-smtp.messagingengine.com [103.168.172.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6A24E1474C4 for ; Fri, 14 Jun 2024 06:42:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=103.168.172.159 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347371; cv=none; b=O70JwaFSJrqOAKAdOWQgBFWz6ts5ZgFEIE9gYRxAVajNKZWOj87HAl8Pte6hWzfprzqGlQMyO8rwpVkrUdFkF+Cno5dBGjKIWcpmQBG4FtYqnlfkhVNBbG/rSpAfc2IF4mcr3dm4svPu0hHgk2enMRNyKGBuDIbYMembBFSz9YI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347371; c=relaxed/simple; bh=x9ROFbzDXc1cZlx2TNR80vtJOy2nxHb/Bhm+XDR+voo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Xq58aKumUMq4+5p3ZUZU6bWtsKBzZRD7gDACfzGqCVwU6A64QdNKhKXfGAJnayShARZFdhkydVqjn2cBWgII3bMSzMDz5eRx4b0lcMFI2FR9IyE8wdD/x1vw+v8HywVZdb4GNP4MGvAWKFNIjAf3Fdwso7siCs9azxZLZ7G2PzI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im; spf=pass smtp.mailfrom=pks.im; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b=M2I6VJK1; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=gr9oT5kI; arc=none smtp.client-ip=103.168.172.159 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pks.im Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b="M2I6VJK1"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="gr9oT5kI" Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 6EB821140107; Fri, 14 Jun 2024 02:42:48 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 14 Jun 2024 02:42:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pks.im; h=cc:cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1718347368; x=1718433768; bh=3dXeY6mywi idKtz+qRQW4Vbi8kalkIpabji1dfEyP6g=; b=M2I6VJK1ZT/xALWbgZzOpR88Xl o7TmVY1CLc09taaClMrodRqqG5s6iaqe1HB5tZle4/kdepoLA53OINJCTgdONmfD BLqABu0nzrIaCHf1o15XFzNa+DMHQqLoT4fY+XbGpXxAhzUXAZPKNgN78y/y8Jrz UpYM6aIE+PQHfrjufN8Qkq8UIV/lC0yesJmRX/Nc9X6dXuLHBIsIh3BmOyFiEqz8 ndv4gZs/kCAAoiWrllOfrRoc2pH6IAzSAjSF58DEPDMo6DFi6mkp/q8h8IQ61yK3 fsyIXVAQdwqGZHJHpLecQMllne9vm0nIk1TIc3g+x8wqzvgiz46QGxCM/DiQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1718347368; x=1718433768; bh=3dXeY6mywiidKtz+qRQW4Vbi8kal kIpabji1dfEyP6g=; b=gr9oT5kIVAs0UPpqrVTmWOjFJUlT0SCa7M4wioOV5lyz AKuBIqbGFXWdGvTpKGBU59f8yO7RveSE4zD4ecRR/euv8StrklkjtzNKE8cCLrDO RsEe2X9kRWCwmx3cwHN7POZav4KDd27MHJRYEOR0BwNS6OLJFd1Kjmu1zTWHokLQ E6xVdVf9TkyI1sm44BfPfKVyrSTQZe5Dy6rYPXq6MYdDbbS59wn6H0yRMp427njs 2SWcqSaPjg719MuGxbcaOw1xyRKTpd+PlIzuovTLU0UZC3mdvgJKeoLPCImwBiLs dHtM5pPYUxvfQgMQV2eAJb1tvN++ky4FiO+MV7VR7g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfedukedguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrrght rhhitghkucfuthgvihhnhhgrrhguthcuoehpshesphhkshdrihhmqeenucggtffrrghtth gvrhhnpeeukedtvedtffevleejtefgheehieegkeeluddvfeefgeehgfeltddtheejleff teenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpsh esphhkshdrihhm X-ME-Proxy: Feedback-ID: i197146af:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Jun 2024 02:42:46 -0400 (EDT) Received: by localhost (OpenSMTPD) with ESMTPSA id f632ce35 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 14 Jun 2024 06:42:31 +0000 (UTC) Date: Fri, 14 Jun 2024 08:42:44 +0200 From: Patrick Steinhardt To: git@vger.kernel.org Cc: Johannes Schindelin , Phillip Wood , Justin Tobler , Junio C Hamano , Dragan Simic , Karthik Nayak , Todd Zullinger Subject: [PATCH v7 3/4] BreakingChanges: document removal of grafting Message-ID: References: Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: The grafting mechanism for objects has been deprecated in e650d0643b (docs: mark info/grafts as outdated, 2014-03-05), which is more than a decade ago. The mechanism can lead to hard-to-debug issues and has a superior replacement with replace refs. Follow through with the deprecation and mark grafts for removal in Git 3.0. Signed-off-by: Patrick Steinhardt --- Documentation/BreakingChanges.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt index 68ad42d805..62695ec2e1 100644 --- a/Documentation/BreakingChanges.txt +++ b/Documentation/BreakingChanges.txt @@ -102,6 +102,19 @@ Cf. <2f5de416-04ba-c23d-1e0b-83bb655829a7@zombino.com>, === Removals +* Support for grafting commits has long been superseded by git-replace(1). + Grafts are inferior to replacement refs: ++ + ** Grafts are a local-only mechanism and cannot be shared across + repositories. + ** Grafts can lead to hard-to-diagnose problems when transferring objects + between repositories. ++ +The grafting mechanism has been marked as outdated since e650d0643b (docs: mark +info/grafts as outdated, 2014-03-05) and will be removed. ++ +Cf. <20140304174806.GA11561@sigill.intra.peff.net>. + == Superseded features that will not be deprecated Some features have gained newer replacements that aim to improve the design in From patchwork Fri Jun 14 06:42:48 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Patrick Steinhardt X-Patchwork-Id: 13697922 Received: from fout1-smtp.messagingengine.com (fout1-smtp.messagingengine.com [103.168.172.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 457B71474C4 for ; Fri, 14 Jun 2024 06:42:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=103.168.172.144 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347376; cv=none; b=ofZouXJIubcIqR3bIkQmTH+pZeTj8HYEjR6xcW6znYaApG13MMPYLH5TSEDQQNIBJofTlOtfBQ1uOvoYY3f8LkESGIryA6XzgXG4puRmltXKu0qmMbrqP+OMyDEKOfSSwami4eSVi1dQGIkbqMYHu61IvakWQqvrbIsWIS/RvAU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1718347376; c=relaxed/simple; bh=E3dr8hn0At9nAgLD6263B/5rIVxvFsIMENDtyVJG/TQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=pDd5rfnVEajyF/rh3eXUN2Sjm+kXG991tiUcQnAX4KVyjgUcM1k12rGSW4ztIl87Uvq+UXA9zm2r7oQv7pYfk6f+zDdXfBSPGHTSTtAuC59iaVCO7NTp1OxID12Bfdn5gHj1DZsyeI0/Sq/2hU08z3SxWjBtlLa9TT/lz/HLL/I= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im; spf=pass smtp.mailfrom=pks.im; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b=kxbjZPr/; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=Ae8vGCIo; arc=none smtp.client-ip=103.168.172.144 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=pks.im Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pks.im Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pks.im header.i=@pks.im header.b="kxbjZPr/"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="Ae8vGCIo" Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.nyi.internal (Postfix) with ESMTP id 3E9041380232; Fri, 14 Jun 2024 02:42:53 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 14 Jun 2024 02:42:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pks.im; h=cc:cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1718347373; x=1718433773; bh=y6vwfFDcsR 8/Ws8PJc5KuaNK0Yel1ifREMMUfqf85Rw=; b=kxbjZPr/b8gWByAkIaFvWnxxot WbhyCY0Lf3cFsS6uFNvTAuzxvAfC5anZglPiKJSS48O+dmvraGDTLlV3aBJpaL1/ L/L1R5OQq89XAvXBbZexql0w4xbOY0RcmWYEUH0xdPtCl8swb8i5oK7cqmvCQFYn Pi+4wSRPlcKt5Of5/VGLZD/zESbtP1ocYn2ij/O0v6AfkHtxdhbfpD2AsYQ7nBsg J4tlsUXsCHeMqmobVBL7mi7igAQH6VzmKwDtA6g2QFbgozWophmkvGlSGVEzgaMm q0HpStYhrwxrQjRJ1qnNWgmy7uZQgL5t2G3xXgYk6b+/mSDgouaSFK5N8HaQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1718347373; x=1718433773; bh=y6vwfFDcsR8/Ws8PJc5KuaNK0Yel 1ifREMMUfqf85Rw=; b=Ae8vGCIoR3RmOLk9QK1JtBuOoLQjghLrqp3IERtbORQ0 2diNqm63jQV2orQb/TwWxASvF40yN80i5h3fRYqModtAn2NSZdF/UMa+M0UMmm5H /xLi4vf9QDrJbJn6c7zXNKjnr2omsejfNvKOJBWoKdiVA5SvFjJMONfL23i5SMv0 RmOO/tMLwI4yH6f9aWJG4sjXZpsb/BZJjusrNFEN7wgZgQzJ1PpYH0bmhuLEJa1l 9Ozha25lFuipJywdwc/gBWh46VSzqPVTLHAIQdqeQguXuFAo3dMWp/Io4pCmfw8Z v/gjALEu/DpPO/vHX9TwS3YQgy4xrlHY6vrKaaUJhw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfedukedguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrrght rhhitghkucfuthgvihhnhhgrrhguthcuoehpshesphhkshdrihhmqeenucggtffrrghtth gvrhhnpeeukedtvedtffevleejtefgheehieegkeeluddvfeefgeehgfeltddtheejleff teenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpsh esphhkshdrihhm X-ME-Proxy: Feedback-ID: i197146af:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Jun 2024 02:42:51 -0400 (EDT) Received: by localhost (OpenSMTPD) with ESMTPSA id 96aa9638 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 14 Jun 2024 06:42:36 +0000 (UTC) Date: Fri, 14 Jun 2024 08:42:48 +0200 From: Patrick Steinhardt To: git@vger.kernel.org Cc: Johannes Schindelin , Phillip Wood , Justin Tobler , Junio C Hamano , Dragan Simic , Karthik Nayak , Todd Zullinger Subject: [PATCH v7 4/4] BreakingChanges: document that we do not plan to deprecate git-checkout Message-ID: <25b20bb0ca84e6c97d27688f5e7a5f28c7ad5d1b.1718345026.git.ps@pks.im> References: Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: The git-checkout(1) command is seen by many as hard to understand because it connects two somewhat unrelated features: switching between branches and restoring worktree files from arbitrary revisions. In 2019, we thus implemented two new commands git-switch(1) and git-restore(1) to split out these separate concerns into standalone functions. This "replacement" of git-checkout(1) has repeatedly triggered concerns for our userbase that git-checkout(1) will eventually go away. This is not the case though: the use of that command is still widespread, and it is not expected that this will change anytime soon. Document that all three commands will remain for the foreseeable future. This decision may be revisited in case we ever figure out that most everyone has given up on any of the commands. Signed-off-by: Patrick Steinhardt --- Documentation/BreakingChanges.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt index 62695ec2e1..ba86c0224d 100644 --- a/Documentation/BreakingChanges.txt +++ b/Documentation/BreakingChanges.txt @@ -121,3 +121,15 @@ Some features have gained newer replacements that aim to improve the design in certain ways. The fact that there is a replacement does not automatically mean that the old way of doing things will eventually be removed. This section tracks those features with newer alternatives. + +* The features git-checkout(1) offers are covered by the pair of commands + git-restore(1) and git-switch(1). Because the use of git-checkout(1) is still + widespread, and it is not expected that this will change anytime soon, all + three commands will stay. ++ +This decision may get revisited in case we ever figure out that there are +almost no users of any of the commands anymore. ++ +Cf. , +, +<112b6568912a6de6672bf5592c3a718e@manjaro.org>.