Re: git apply vs patch -p1 - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: git apply vs patch -p1
Date
Msg-id 8738p47feh.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: git apply vs patch -p1  (Josh Berkus <josh@agliodbs.com>)
Responses Re: git apply vs patch -p1
List pgsql-hackers
>>>>> "Josh" == Josh Berkus <josh@agliodbs.com> writes:
Josh> The issue isn't that, it's that git apply is just buggy andJosh> can't tell the difference between a new file and
amodifiedJosh> one.
 

It's not the fault of git apply; the patch contained explicit
annotations on all the files claiming that they were new. Both the
patches I've looked at so far (picksplit NaNs and enable_material)
had the same defect.

The question is, how are these submitters preparing their patches?

-- 
Andrew (irc:RhodiumToad)



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: git apply vs patch -p1
Next
From: Pavel Stehule
Date:
Subject: Re: Assertions in PL/PgSQL