git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: greened@obbligato.org (David A. Greene)
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, techlivezheng@gmail.com,
	alex.crezoff@gmail.com, davvid@gmail.com,
	cbailey32@bloomberg.net, danny0838@gmail.com, prohaska@zib.de,
	th.acker@arcor.de, sschuberth@gmail.com, peff@peff.net,
	gitter.spiros@gmail.com, nod.helm@gmail.com
Subject: Re: [PATCH] contrib/subtree: Remove --annotate
Date: Sun, 17 Jan 2016 17:30:14 -0600	[thread overview]
Message-ID: <87oacjaint.fsf@waller.obbligato.org> (raw)
In-Reply-To: <xmqqbn8mish5.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Fri, 15 Jan 2016 10:54:14 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> greened@obbligato.org (David A. Greene) writes:
>
>> If you really don't want to get rid of this, I guess that's ok but my
>> preference as maintainer is to reduce the feature set to those things
>> people seem to actually regularly use (according to my very unscientific
>> Google searches) and add features as requested/evaluated.  --annotate
>> isn't a huge maintenance burdern but some of those other changes I
>> mentioned do in fact significantly reduce the maintenance burden of
>> git-subtree.  I hope I will have some leeway with those, even if they
>> change semantics slightly.
>
> OK.  It is easy enough to add back when people complains, so...
>
> ;-)

Thanks.

Just to clarify, what is the expectation of things in contrib?
Basically the same as other code?

                    -David

  reply	other threads:[~2016-01-17 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  3:05 [PATCH v2] Remote subtree split --annotate David Greene
2016-01-05  3:05 ` [PATCH] contrib/subtree: Remove --annotate David Greene
2016-01-05 17:33   ` Junio C Hamano
2016-01-05 21:35     ` David A. Greene
2016-01-15 18:54       ` Junio C Hamano
2016-01-17 23:30         ` David A. Greene [this message]
2016-01-18  1:29           ` Junio C Hamano
2016-06-28 11:10             ` David A. Greene
  -- strict thread matches above, loose matches on Subject: below --
2016-01-02 20:36 Remote subtree split --annotate David Greene
2016-01-02 20:36 ` [PATCH] contrib/subtree: Remove --annotate David Greene
2016-01-03  9:06   ` Sebastian Schuberth
2016-01-04 15:53     ` greened

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=87oacjaint.fsf@waller.obbligato.org \
    --to=greened@obbligato.org \
    --cc=alex.crezoff@gmail.com \
    --cc=cbailey32@bloomberg.net \
    --cc=danny0838@gmail.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=gitter.spiros@gmail.com \
    --cc=nod.helm@gmail.com \
    --cc=peff@peff.net \
    --cc=prohaska@zib.de \
    --cc=sschuberth@gmail.com \
    --cc=techlivezheng@gmail.com \
    --cc=th.acker@arcor.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. 
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).