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

Re: [PATCH] Fix rename/copy when dealing with temporarily broken pairs.

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jun 13, 2005, 22:17 UTC
Message-ID
<2cfc403205061315173f8095b8@mail.gmail.com>
In-Reply-To
<7vis0ic6ot.fsf@assigned-by-dhcp.cox.net>
On 6/14/05, Junio C Hamano <junkio@cox.net> wrote:
> JS> I wondered if this patch might fix it, but it doesn't seem to.
> Regular "patch" cannot grok either copy or rename.  If your
> recipient uses "patch", then you must not use -C nor -M when you
> are preparing a diff for his consumption.

Ok, there was no problem other than me not understanding what git-apply did - thank you Pasky for bringing light to the dark regions of my sleep-deprived brain!

jon.
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 7 in “read-tree: loosen too strict index requirements”
  1. 5/3 read-tree: loosen too strict index requirementsJunio C Hamano, Jun 11, 2005
  2. Fix rename/copy when dealing with temporarily broken pairs.Junio C Hamano, Jun 12, 2005
  3. Jon SeymourJun 13, 2005
  4. Petr BaudisJun 13, 2005
  5. Junio C HamanoJun 13, 2005
  6. Jon SeymourJun 13, 2005
  7. Add --diff-filter= output restriction to diff-* family.Junio C Hamano, Jun 12, 2005

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.