All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <bebarino@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder@ira.uka.de>
Subject: Re: [PATCH 7/7] fmt-merge-msg: hide summary option
Date: Wed, 24 Mar 2010 22:19:32 -0700	[thread overview]
Message-ID: <4BAAF264.7050003@gmail.com> (raw)
In-Reply-To: <7v4ok5dsqr.fsf@alter.siamese.dyndns.org>

On 03/24/2010 07:45 PM, Junio C Hamano wrote:
> We could do that sometime in this autumn timeframe if we start making
> noises when they are used, just like we did during the 1.7.0 transition
> against soon-to-be-deprecated "features".

We already make noises when the option is used. Probably need to make
some noises in release notes though.

> Are there other ancient features we have been passively advertising as
> deprecated that we should now start the removal process?

grepping for deprecated shows mostly deprecated commands:

    git lost-found
    git tar-tree
    git peek-remote (synonym to git ls-remote)
    git init-db (synonym to git init)
    git repo-config (synonym to git config)

I'm pretty sure we don't want to remove them anytime soon though, right?

The only option of interest is 'git reset --mixed' with paths. I don't
really know the backstory on that but it looks like it was deprecated
when the command was made into a builtin 0e5a7fa (Make "git reset" a
builtin., 2007-09-11). Maybe it can become a die now?

Oh and git notes has a deprecation warning but I think we'll probably
have to revisit that one in a few years.

  reply	other threads:[~2010-03-25  5:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24  7:15 [PATCH 0/7] fmt-merge-msg improvements Stephen Boyd
2010-03-24  7:15 ` [PATCH 1/7] fmt-merge-msg: be quiet if nothing to merge Stephen Boyd
2010-03-25  2:39   ` Junio C Hamano
2010-03-25  3:48     ` Stephen Boyd
2010-03-24  7:15 ` [PATCH 2/7] t6200: modernize with test_tick Stephen Boyd
2010-03-24  7:16 ` [PATCH 3/7] t6200: test fmt-merge-msg more Stephen Boyd
2010-03-24  7:16 ` [PATCH 4/7] fmt-merge-msg: use pretty.c routines Stephen Boyd
2010-03-24  7:16 ` [PATCH 5/7] string-list: add unsorted_string_list_lookup() Stephen Boyd
2010-03-24  7:16 ` [PATCH 6/7] fmt-merge-msg: remove custom string_list implementation Stephen Boyd
2010-03-30  5:18   ` Junio C Hamano
2010-04-01  6:08     ` Stephen Boyd
2010-04-01  6:29     ` [PATCH 8/7] Make string_list_append() consistent with everything else Stephen Boyd
2010-04-01 20:07       ` Julian Phillips
2010-03-24  7:16 ` [PATCH 7/7] fmt-merge-msg: hide summary option Stephen Boyd
2010-03-25  2:45   ` Junio C Hamano
2010-03-25  5:19     ` Stephen Boyd [this message]
2010-03-26 19:30       ` 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

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

  git send-email \
    --in-reply-to=4BAAF264.7050003@gmail.com \
    --to=bebarino@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder@ira.uka.de \
    /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.