Re: [ANNOUNCE] Git v2.24.0-rc1

From: Elijah Newren <newren@gmail.com>
Date: Oct 30, 2019, 06:56 UTC
Message-ID: <CABPp-BGV=5FuMfq1pYbbHCMMvyVGQPS_8yTjqhKoqrm7O1KFow@mail.gmail.com>
In-Reply-To: <xmqqeez2fzsy.fsf@gitster-ct.c.googlers.com>

Hi Junio,

A couple questions on the release notes...

On Thu, Oct 24, 2019 at 1:35 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

> Git 2.24 Release Notes (draft)
> ==============================
>
> Updates since v2.23
> -------------------
>
> Backward compatibility note
>
>  * Although it is not officially deprecated, "filter-branch" is
>    showing its age and alternatives are available.  From this release,
>    we started to discourage its uses and hint people about
>    filter-repo.

What do you mean by deprecation, then?

My understanding has always been that deprecation meant "supported but discouraged", which is exactly what we're doing. We also run the risk of people seeing "not officially deprecated" in the release notes, then being very confused why the documentation and the program itself is discouraging its own use and wonder if they configured things wrong or got the wrong version of git ("The release notes says it isn't deprecated, but whatever version I'm running definitely does have it deprecated. What'd I do wrong??").

>  * The merge-recursive machiery is one of the most complex parts of

I fixed this "machiery" typo in en/doc-typofix but as that hasn't even merged down to next yet, I'm wondering if you're planning to include that in the release. Should I provide a subset of those fixes in a separate patch for inclusion in the 2.24 release? Which of the types of doc typo fixes would you want to see at this point for including?