From: | Tony Wayne <anonymouslydark3(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: How to send patch with so many files changes? |
Date: | 2024-09-25 00:49:39 |
Message-ID: | CAAW5B8ygSaMRcgQGn1+iiTrLTkJ0vK=ch+FddtCzMHi4o3JU7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
These changes are for core ,I think it would be better to either move whole
changes to core or contrib as an extension.
On Wed, Sep 25, 2024 at 6:09 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Tue, Sep 24, 2024 at 5:37 PM Tony Wayne <anonymouslydark3(at)gmail(dot)com>
> wrote:
>
>>
>> On Wed, Sep 25, 2024 at 6:02 AM Tony Wayne <anonymouslydark3(at)gmail(dot)com>
>> wrote:
>>
>>>
>>> I am new in contributing to postgres. I have a doubt regarding if we
>>> want to send a patch which has an extension and also has changes in pg
>>> source also,what's the way to do it?
>>>
>>> is git diff enough?
>>
>
> Usually you'd want to use format-patch so your commit message(s) make it
> into the artifact. Especially for something complex/large.
>
> David J.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-09-25 01:06:38 | Re: How to send patch with so many files changes? |
Previous Message | Thomas Munro | 2024-09-25 00:45:10 | Re: AIO writes vs hint bits vs checksums |