From: John Keeping <john@keeping.me.uk>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH 0/4] Remove deprecated commands
Date: Mon, 11 Nov 2013 21:10:42 +0000 [thread overview]
Message-ID: <20131111211042.GR24023@serenity.lan> (raw)
In-Reply-To: <20131111191345.GL10302@google.com>
On Mon, Nov 11, 2013 at 11:13:45AM -0800, Jonathan Nieder wrote:
> John Keeping wrote:
> > On Mon, Nov 11, 2013 at 10:25:51AM -0800, Junio C Hamano wrote:
> >> John Keeping <john@keeping.me.uk> writes:
>
> >>> "git repo-config", "git tar-tree", "git lost-found" and "git
> >>> peek-remote" have all been deprecated since at least Git 1.5.4.
> [...]
> >> Probably good material to discuss during the next cycle.
> [...]
> > I was assuming these would be queued as a "held until 2.0" branch, but
>
> Please no. :) We already have a nice set of features for 2.0 and I
> hope people have as few excuses not to upgrade as possible. Anything
> that actually needs the same kind of treatment that is introduced now
> should wait for 3.0.
>
> Removing repo-config, tar-tree, and peek-remote sounds fine to me
> (though I haven't thought much about it either way) and I agree that
> it wouldn't need to wait for an x.0 release.
For "git repo-config", the 1.5.4 release notes say that it will "be
removed in the next feature release". I'm not sure what a "feature
release" is, but if 1.6.0 wasn't one, then I think 2.0 will be the next
one.
Although, I now see that howto/maintain-git.txt says a feature release
is numbered vX.Y.Z, so perhaps it should have been removed long before
now...
prev parent reply other threads:[~2013-11-11 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 15:47 [RFC/PATCH 0/4] Remove deprecated commands John Keeping
2013-11-10 15:47 ` [RFC/PATCH 1/4] repo-config: remove deprecated alias for "git config" John Keeping
2013-11-10 15:47 ` [RFC/PATCH 2/4] tar-tree: remove deprecated command John Keeping
2013-12-02 23:37 ` [PATCH jk/remove-deprecated] stop installing git-tar-tree link Jonathan Nieder
2013-12-03 20:19 ` John Keeping
2013-12-04 10:23 ` Michael J Gruber
2013-11-10 15:47 ` [RFC/PATCH 3/4] lost-found: remove deprecated command John Keeping
2013-11-10 15:47 ` [RFC/PATCH 4/4] peek-remote: remove deprecated alias of ls-remote John Keeping
2013-11-11 18:25 ` [RFC/PATCH 0/4] Remove deprecated commands Junio C Hamano
2013-11-11 18:38 ` John Keeping
2013-11-11 19:13 ` Jonathan Nieder
2013-11-11 21:10 ` John Keeping [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=20131111211042.GR24023@serenity.lan \
--to=john@keeping.me.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.