From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.24.0-rc1
Date: Sat, 02 Nov 2019 12:25:12 +0900 [thread overview]
Message-ID: <xmqqh83n559j.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BGV=5FuMfq1pYbbHCMMvyVGQPS_8yTjqhKoqrm7O1KFow@mail.gmail.com> (Elijah Newren's message of "Tue, 29 Oct 2019 23:56:50 -0700")
Elijah Newren <newren@gmail.com> writes:
> 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:
>> 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.
You probably want to question the "officially" part. My
understading is that some vocal members of the community
may be advocating for the official deprecation, and I am
more or less in agreement, but haven't heard from enough
folks to make it "official" community consensus just yet.
prev parent reply other threads:[~2019-11-02 3:25 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
2019-11-02 3:25 ` Junio C Hamano [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh83n559j.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).