From: Jeff King <peff@peff.net>
To: David Roundy <roundyd@physics.oregonstate.edu>
Cc: git@vger.kernel.org
Subject: Re: confusion with git diff-tree output
Date: Thu, 22 Oct 2009 20:54:26 -0400 [thread overview]
Message-ID: <20091023005426.GA2431@sigill.intra.peff.net> (raw)
In-Reply-To: <117f2cc80910211523m5c1399aej594398fb6597e5de@mail.gmail.com>
On Wed, Oct 21, 2009 at 06:23:08PM -0400, David Roundy wrote:
> You're right. I figured I must be overlooking something obvious, and
> that was it. What surprised me was that -p implies -r, which is not
> documented. Since the -p output was recursive, I incorrectly presumed
> that this was the default.
It's due to hysterical raisins:
http://article.gmane.org/gmane.comp.version-control.git/54078
-Peff
next prev parent reply other threads:[~2009-10-23 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 17:43 confusion with git diff-tree output David Roundy
2009-10-21 17:51 ` Jan Krüger
2009-10-21 22:23 ` David Roundy
2009-10-21 22:42 ` Jan Krüger
2009-10-23 0:54 ` Jeff King [this message]
2009-10-24 6:36 ` Junio C Hamano
2009-10-24 9:51 ` Jeff King
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=20091023005426.GA2431@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=roundyd@physics.oregonstate.edu \
/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).