On Tue, Oct 29, 2019 at 11:56 PM Elijah Newren <newren@xxxxxxxxx> wrote:
>
> Hi Junio,
>
> A couple questions on the release notes...
>
> On Thu, Oct 24, 2019 at 1:35 PM Junio C Hamano <gitster@xxxxxxxxx> wrote:
> > 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?
Made a guess at the answers to my questions in the form of patches:
https://public-inbox.org/git/pull.440.git.1572466878.gitgitgadget@xxxxxxxxx/
