From: Jeff King <peff@peff.net>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git log: why are --full-diff and --pickaxe-all separate options?
Date: Wed, 24 Mar 2010 12:20:06 -0400 [thread overview]
Message-ID: <20100324162005.GA6626@sigill.intra.peff.net> (raw)
In-Reply-To: <76718491003240852m2a2c12afjca2c71f6c78b2047@mail.gmail.com>
On Wed, Mar 24, 2010 at 11:52:13AM -0400, Jay Soffian wrote:
> But now I wonder why these are separate options. Is there any reason
> they shouldn't be unified?
I agree it is confusing, and the answer is "maybe". A long and gory
explanation can be found here:
http://article.gmane.org/gmane.comp.version-control.git/34909
Read the later messages in the thread from Junio, too, as he goes back
and forth a bit. I don't remember if anything happened after that, or
why not.
-Peff
next prev parent reply other threads:[~2010-03-24 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 15:52 git log: why are --full-diff and --pickaxe-all separate options? Jay Soffian
2010-03-24 16:20 ` Jeff King [this message]
2010-03-24 17:19 ` 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=20100324162005.GA6626@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jaysoffian@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 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).