From: Junio C Hamano <junkio@cox.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: when is "git diff" output suitable for patch?
Date: Thu, 13 Jul 2006 14:51:20 -0700 [thread overview]
Message-ID: <7v3bd5uqav.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060713213116.GK19366@fieldses.org> (J. Bruce Fields's message of "Thu, 13 Jul 2006 17:31:16 -0400")
"J. Bruce Fields" <bfields@fieldses.org> writes:
>> As far as I recall "git diff" never defaulted to -M.
>
> Hm. Is this related?:
>
> commit 42efbf6d8a5b4902c55a2f6e96034625c056ba1f
> Author: Junio C Hamano <junkio@cox.net>
> Date: Sat Mar 11 17:44:10 2006 -0800
>
> git-diff: -p disables rename detection.
Ah, sorry, it _did_ default to -M; it was in such an ancient
past and the shell wrapper wasn't initially done by me, so I
misremembered.
next prev parent reply other threads:[~2006-07-13 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 21:21 when is "git diff" output suitable for patch? J. Bruce Fields
2006-07-13 21:27 ` Junio C Hamano
2006-07-13 21:31 ` J. Bruce Fields
2006-07-13 21:51 ` Junio C Hamano [this message]
2006-07-13 21:53 ` J. Bruce Fields
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=7v3bd5uqav.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=bfields@fieldses.org \
--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).