archive mirror
 help / color / mirror / Atom feed
From: Elijah Newren <>
To: Junio C Hamano <>
Cc: Git Mailing List <>
Subject: Re: [ANNOUNCE] Git v2.24.0-rc1
Date: Wed, 30 Oct 2019 13:52:54 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Oct 29, 2019 at 11:56 PM Elijah Newren <> wrote:
> Hi Junio,
> A couple questions on the release notes...
> On Thu, Oct 24, 2019 at 1:35 PM Junio C Hamano <> 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:

  reply	other threads:[~2019-10-30 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  6:00 [ANNOUNCE] Git v2.24.0-rc1 Junio C Hamano
2019-10-24 22:46 ` Git for Windows v2.24.0-rc1, was " Johannes Schindelin
2019-10-30  6:56 ` Elijah Newren
2019-10-30 20:52   ` Elijah Newren [this message]
2019-11-02  3:25   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).