From: Karl Hasselström <kha@treskal.com>
Date: Thu, 26 Jun 2008 12:49:27 GMT
Subject: Re: git-diff/git-format-patch safe for GNU (or POSIX) patch?
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:

> 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