From: Mark Burton <markb@ordern.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: RFC: Change whatchanged to report changes from merges by default?
Date: Sat, 20 Dec 2008 20:21:09 +0000 [thread overview]
Message-ID: <20081220202109.336d0a5e@crow> (raw)
In-Reply-To: <7vvdtewqvy.fsf@gitster.siamese.dyndns.org>
On Sat, 20 Dec 2008 12:09:05 -0800
Junio C Hamano <gitster@pobox.com> wrote:
> IOW, I consider "whatchanged" a command that is kept only for old timers'
> sake. There is no reason to promote it, but there is no reason to
> deprecate it, either. Which means the answer to this question...
>
> > Would it not make more sense to have git whatchanged show the changes
> > introduced by merges by default and then people can use the (already
> > supported) --no-merges option to suppress that behaviour?
>
> ... is a NO spelled in capital letters.
OK (spelled in capital letters), I won't submit the patch.
Cheers,
Mark
prev parent reply other threads:[~2008-12-20 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 10:42 RFC: Change whatchanged to report changes from merges by default? Mark Burton
2008-12-20 17:22 ` Mark Burton
2008-12-20 20:09 ` Junio C Hamano
2008-12-20 20:21 ` Mark Burton [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=20081220202109.336d0a5e@crow \
--to=markb@ordern.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).