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

Re: git-diff/git-format-patch safe for GNU (or POSIX) patch?

From
Karl Hasselström <kha@treskal.com>
Date
Jun 26, 2008, 12:49 UTC
Message-ID
<20080626124927.GA17731@diana.vm.bytemark.co.uk>
In-Reply-To
<58284.213.203.159.164.1214480989.squirrel@upmail.polettix.it>
On 2008-06-26 13:49:49 +0200, Flavio Poletti wrote:
Show 5 quoted lines
> Importing wasn't actually an issue, just a matter of
> init/add/commit. I was more scared about the patch production
> process, i.e. producing a patch that could be perfectly usable by
> the project's maintainers. But given what you kindly said, I think I
> can dismiss this as excess of caution by me.

Yes, patch is one of the most permissive programs around. It will eat _anything_. (And throw up on the carpet if it was just too wrong.)

There are two things in git patches that patch won't grok: rename/copy patches, and binary patches. Neither feature is on by default, IIRC -- you have to give command line flags -- precisely so that "git diff" default output will be patch compatible.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Flavio PolettiNext: Petr Baudis
Message 4 of 5 in “git-diff/git-format-patch safe for GNU (or POSIX) patch?”
  1. Flavio PolettiJun 26, 2008
  2. Karl HasselströmJun 26, 2008
  3. Flavio PolettiJun 26, 2008
  4. Karl HasselströmJun 26, 2008
  5. Petr BaudisJun 26, 2008

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.