From: Kristoffer Haugsbakk Date: Thu, 16 Oct 2025 17:42:03 GMT Subject: Re: [PATCH] BreakingChanges: say that `git diff X..Y` syntax will be removed in 3.0 Message-ID: In-Reply-To: On Thu, Oct 16, 2025, at 01:06, Martin von Zweigbergk wrote: > On Wed, 15 Oct 2025 at 15:19, Junio C Hamano wrote: >>[snip] >> >> In any case, a declaration that does not come with code changes that >> are protected by WITH_BREAKING_CHANGES CPP macro is a patch that is >> not quite ready to be applied. > > Yeah, this was meant as a discussion starter. I assumed I had missed a > few things as I'm not very familiar with how things are done here. I'm > happy to add that WITH_BREAKING_CHANGES macro if there's a V2. Is one potential outcome just to deprecate the notations without slating them for removal right away? According to the current document it seems that only `core.commentString=auto` has been both deprecated and slated for removal during the same release cycle. It looks like everything else was deprecated for a good while before the Git 3.0 plan. Maybe ref files → reftable as well although that doesn’t deprecate anything.