From: Jay Soffian <jaysoffian@gmail.com>
To: git <git@vger.kernel.org>
Subject: git log: why are --full-diff and --pickaxe-all separate options?
Date: Wed, 24 Mar 2010 11:52:13 -0400 [thread overview]
Message-ID: <76718491003240852m2a2c12afjca2c71f6c78b2047@mail.gmail.com> (raw)
I just did this:
$ git log -p -- /some/path
And didn't get the full commit. I know about the --pickaxe-all option,
so I optimistically tried:
$ git log -p --pickaxe-all -- /some/path
Which of course, does not do what I want. Eventually I found in the
man page that I can do this:
$ git log -p --full-diff -- /some/path
But now I wonder why these are separate options. Is there any reason
they shouldn't be unified?
Regardless, perhaps --pickaxe-all without -S and --full-diff without
-p should be errors?
j.
next reply other threads:[~2010-03-24 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 15:52 Jay Soffian [this message]
2010-03-24 16:20 ` git log: why are --full-diff and --pickaxe-all separate options? Jeff King
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=76718491003240852m2a2c12afjca2c71f6c78b2047@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
/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).