From: Junio C Hamano <gitster@pobox.com>
To: Stephen Boyd <bebarino@gmail.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: Fri, 26 Mar 2010 12:30:40 -0700 [thread overview]
Message-ID: <7vpr2qlw2n.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4BAAF264.7050003@gmail.com> (Stephen Boyd's message of "Wed\, 24 Mar 2010 22\:19\:32 -0700")
Stephen Boyd <bebarino@gmail.com> writes:
> 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.
Then it would be one of the 1.7.2 items, I guess, as we haven't shipped
1.7.1 yet.
prev parent reply other threads:[~2010-03-26 19:30 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
2010-03-26 19:30 ` 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=7vpr2qlw2n.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--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 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).