Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oCNvD-0005ci-0R for pgsql-novice@arkaria.postgresql.org; Fri, 15 Jul 2022 16:12:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oCNvB-000685-61 for pgsql-novice@arkaria.postgresql.org; Fri, 15 Jul 2022 16:12:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oCNvA-00067w-S6 for pgsql-novice@lists.postgresql.org; Fri, 15 Jul 2022 16:12:04 +0000 Received: from mail-ed1-x52c.google.com ([2a00:1450:4864:20::52c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oCNv5-000117-JF for pgsql-novice@lists.postgresql.org; Fri, 15 Jul 2022 16:12:04 +0000 Received: by mail-ed1-x52c.google.com with SMTP id r6so6903013edd.7 for ; Fri, 15 Jul 2022 09:11:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nHVN9CM0EYGr/aWBHuvb1DWK/Z7xcfy3QettnP/W1WE=; b=IZi+s5TRgqO6i4oWdzdNyQgTU7wHDJ9L3yqitZauwakjYizqUUjw4/lIzRuA8FYX1b bSHrlIMgiKY8azqabBy4aotWwnTe37UKPgrNeD3GZhFcdyY587WfQTPhN+wCJkfm+72M /3SnotHRdBd1c69xMb+tYmyox1NkkYa5FI+TqgwxPc8Yl+04uA7CbZMXDkrtvv7JdbqB +pFRS64j1wEMRg8Si3bu5qeY3IAT5r0YBt5T9PU8d3Xb6PcXe6BfIsN1gEeVebd+OzBy U2qsUWbWWnK53gAop8pziVnXbXXVZL36MbmOzRS2VFaEpkpEyQdaFQLJm0ZVVIxnTJhz MwUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nHVN9CM0EYGr/aWBHuvb1DWK/Z7xcfy3QettnP/W1WE=; b=qlPJ03svoqTiC8Fht/kA5/0FOW7khIhm0zEQ900oU3yMd7bB4CpjqH2Fd8OohJKGMH mQ3N7MYLVKa8Pk69IxaFEEqsk4D/yC0TRRZXfaom9t2ahO+YWDNnI8J56RNN+JNOHekr mqOk0E8ihw7oNcu/lQOzNZNdixObaL+YhS6rWZ4FwiD5waxANBpAjKDc3bM1ldmomWIk sGpSPZTIjKNf/sQh5UwR2sfvnCylsb3L0WFCRzgYNDyqwxduJ0tErpbphwSpUuT4Jttf 9+zJmVgcB0f1Vn6T32loDj2EGecgTc7c0DV9JwqQItvkYz+YrJwrAZzrKsQRP+jGepoL L9wg== X-Gm-Message-State: AJIora93SemJBAgOZ2w0XfV9/Ped+6QlQBAgm+7uQ73pC9VJAvOVPmwv eO3hQYG/+VJ6gNw3Hfxs1vMQeimi63pTdNaaFdk= X-Google-Smtp-Source: AGRyM1v2Q27I9R9FKfdqLehxzimsv+PxpyH4VBDZh6n30KqrSPdDIsIlYNpdozw8/h2ToiXyRWnlajjxRsF6gZCqzLA= X-Received: by 2002:a05:6402:1658:b0:43a:91cd:2ffb with SMTP id s24-20020a056402165800b0043a91cd2ffbmr19418862edx.277.1657901517514; Fri, 15 Jul 2022 09:11:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Fri, 15 Jul 2022 09:11:40 -0700 Message-ID: Subject: Re: best way to apply and work on the patches of the pg community To: mahendrakar s Cc: pgsql-novice Content-Type: multipart/alternative; boundary="000000000000062a3305e3da4777" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000062a3305e3da4777 Content-Type: text/plain; charset="UTF-8" On Fri, Jul 15, 2022 at 8:33 AM mahendrakar s 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. --000000000000062a3305e3da4777 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jul 15, 2022 at 8:33 AM mahendrakar s <mahendrakarforpg@gmail.com> w= rote:
Hi Pg team,=

I would like to work on a patch published on hackers co= mmunity( patch is from June, 2021). I cloned postgres code and tried to=C2= =A0 apply the patch and got errors.

patc= h -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?

<= /div>

I'm still in a bit of trial-and-err= or mode myself but I try to use `git apply` first, possibly after making su= re that the files are newline only line endings.

David= J.
--000000000000062a3305e3da4777--