| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | mahendrakar s <mahendrakarforpg(at)gmail(dot)com> |
| Cc: | pgsql-novice <pgsql-novice(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: best way to apply and work on the patches of the pg community |
| Date: | 2022-07-15 16:11:40 |
| Message-ID: | CAKFQuwayR4V2YCtCx=aqoca_gV2ysoAoa0Vj87StPU7QQO8ktw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Fri, Jul 15, 2022 at 8:33 AM mahendrakar s <mahendrakarforpg(at)gmail(dot)com>
wrote:
> Hi Pg team,
>
> I would like to work on a patch published on hackers community( patch is
> from June, 2021). I cloned postgres code and tried to apply the patch and
> got errors.
>
> *patch -p1 < ../0001-auth-generalize-SASL-mechanisms.patch*
> patching file src/backend/libpq/auth-scram.c
> Hunk #1 FAILED at 101.
> Hunk #2 FAILED at 170.
> Hunk #3 FAILED at 199.
> Hunk #4 FAILED at 215.
> Hunk #5 FAILED at 325.
>
> Can you please let me know what is the recommended way to apply the
> patches for me to begin the work?
>
>
I'm still in a bit of trial-and-error mode myself but I try to use `git
apply` first, possibly after making sure that the files are newline only
line endings.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-07-15 16:33:34 | Re: best way to apply and work on the patches of the pg community |
| Previous Message | mahendrakar s | 2022-07-15 15:33:04 | best way to apply and work on the patches of the pg community |