From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Jeff King" <peff@peff.net>
Subject: Re: [RFC/PATCH] WIP: add deprecation & experimental process/interface
Date: Sun, 28 May 2017 10:18:31 +0900 [thread overview]
Message-ID: <xmqqy3thaie0.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170527111032.30897-1-avarab@gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sat, 27 May 2017 11:10:32 +0000")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> The plan, subject to RFC feedback is to:
>
> * Add a new config variable `core.version`. E.g. `core.version =
> 2.14.0` With this the user can specify that they'd like
> new/experimental features introduced in that version (and below),
> as well as immediately getting new deprecations added in that
> version as errors.
>
> This is similar to perl's "use v<VERSION>".
As long as this does not require very new version like v3.0.0 of Git
to pretend as if the user is still running an ancient v2.14.0, it is
a sensible proposal, I would think.
> * Add a deprecated() function to to mark deprecated features.
> * TODO: Add an experimental() function to mark experimental features.
Having burned by bitter experience during v1.6.0 transition, I do
welcome an attempt to make it easier to communicate deprecation
plans to end-users.
next prev parent reply other threads:[~2017-05-28 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 11:10 [RFC/PATCH] WIP: add deprecation & experimental process/interface Ævar Arnfjörð Bjarmason
2017-05-28 1:18 ` Junio C Hamano [this message]
2017-05-29 1:09 ` Junio C Hamano
2017-05-29 11:11 ` Ævar Arnfjörð Bjarmason
2017-05-29 10:23 ` Duy Nguyen
2017-05-29 11:20 ` Ævar Arnfjörð Bjarmason
2017-05-29 14:38 ` Jeff King
2017-05-30 0:56 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy3thaie0.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).