git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: when is "git diff" output suitable for patch?

From
JFJ. Bruce Fields <bfields@fieldses.org>
Date
Jul 13, 2006, 21:53 UTC
Message-ID
<20060713215313.GO19366@fieldses.org>
In-Reply-To
<7v3bd5uqav.fsf@assigned-by-dhcp.cox.net>
On Thu, Jul 13, 2006 at 02:51:20PM -0700, Junio C Hamano wrote:
Show 15 quoted lines
> "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.
Perfectly understandable; thanks for the help.--b.
Previous: Junio C Hamano
Message 5 of 5 in “when is "git diff" output suitable for patch?”
  1. J. Bruce FieldsJul 13, 2006
  2. Junio C HamanoJul 13, 2006
  3. J. Bruce FieldsJul 13, 2006
  4. Junio C HamanoJul 13, 2006
  5. J. Bruce FieldsJul 13, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.