Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tqDep-001NYT-JO for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Mar 2025 16:01:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tqDeo-00GERJ-5S for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Mar 2025 16:01:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tqDen-00GEQd-Rx for pgsql-hackers@lists.postgresql.org; Thu, 06 Mar 2025 16:01:09 +0000 Received: from mail-lj1-x22c.google.com ([2a00:1450:4864:20::22c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tqDel-001KNe-0p for pgsql-hackers@lists.postgresql.org; Thu, 06 Mar 2025 16:01:08 +0000 Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-30b936ffc51so6740621fa.2 for ; Thu, 06 Mar 2025 08:01:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeltef.nl; s=google; t=1741276865; x=1741881665; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dNfuQkyQltrdG+qIlZAGsiY5T4ySJgzi52eBQmLg7gY=; b=mI4uZ2XfwqFqNaiVwpJ1DToEJ0j7JbKYuIrkepDsjn4E+/bADgfphC4RutjapPeuPe CgSkGmbvSI+Ci4lZFjWXatVNf4+b4NS63C8bfHYdZ7UtXhvGdqbz521P68ljbuXpjaYp aQ5/Q2uGwO3XcC2a92lUlS2qhs9fC3mKWiO4TKLc0Gvl1xyGaofMWHIgFjbbz7u/KpTA caaSp2Wt3coCN2GWFv6lV6Q61wK4YhEeDJOBo1eQBk4oCCXOtMGJMmOof03UrpCX6HJU tznkDCQ5Cb+WwkxvcghtzkqgQc8nzPLUR8arF1TOVOHGxbNvzT0M5rjkb5buPYdrNrH8 +PgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741276865; x=1741881665; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dNfuQkyQltrdG+qIlZAGsiY5T4ySJgzi52eBQmLg7gY=; b=YVDFpxIsW89mlAYdg8h2ZTFuLJFV491FzI8Yk9o5seIKCDpTDf+yDrOE3HpfM7ryGZ vuy88aKOZjPQkn6qmTjDvGBi1t0LiizMbKy0YGJ6SoX5EPIvq2dchygIy4D0WioMcs9S YFljBEMbX/0TP9uuf0OELVFlTIrI38+RJYcRb9f9UfQR07E6S09wr2jcQGKAK8azOQ+g U1xl+FbxoPYKu3pNl7VuSJ6QIc1/ZLdcM5su4gpJXCL0sFn82Kj02qCp0S/gBz9YNTAC DIeJdqqzJMNNhx8CZn9WOMrS9Lifij1LH+AKPVkx0ArIP0rUdB+UoOYpwiSiVNSG2Cp/ f68Q== X-Gm-Message-State: AOJu0Yw52VzlB5cm2ozrEn0kUwyerQbaYe/EAyM2gJ03sNvQyJmTCMeB FYA+aKrTuJ+W3+hEm1/yAeE/boGjhYmx8VghgYumahUJZzWOihbTRLCacStAK6q0rp7Xphozrb/ RcrhYp2WGdzdhblsjnm8BHGMiGuGGXiSs8DHLUw== X-Gm-Gg: ASbGncumcDFiLuxGtyPIeON/I/WJbkI8p2DBTrYR5PyyNg1jQe4Ri4QwUHjXWu9rs/n VJgAH3Gqv/9FWwemDnOlsWrJn+proKztqZUB2nnMS/MwhK8C1Wegf0Nprvbj3PpThWecjoZWomW 6SBsVP4z16H9RVI6+NsN+3WZgE1do= X-Google-Smtp-Source: AGHT+IHIbG4jeozM3u2Qpy9WNHPbTk5XhDWwhFHMWY+eMsR3XKKeq7EFX+OYZx3Yauq9dNF4S8qGI0vOD6D1V0Q9VYo= X-Received: by 2002:a05:6512:32a6:b0:549:8b24:9896 with SMTP id 2adb3069b0e04-5498b249ac8mr912873e87.0.1741276863464; Thu, 06 Mar 2025 08:01:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jelte Fennema-Nio Date: Thu, 6 Mar 2025 17:00:52 +0100 X-Gm-Features: AQ5f1JoJZiuWQvKdcQ0eP_WC2sgRcw892F3rdhVJWqPxWWnVWf4DFQE-UiuccdA Message-ID: Subject: Re: Commitfest app release on Feb 17 with many improvements To: vignesh C Cc: PostgreSQL Hackers , Jacob Brazeal Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 6 Mar 2025 at 16:36, vignesh C wrote: > But it applies neatly for me and Jim also at [3]. Any idea why patch > apply fails with CFbot whereas it passes in our environment? Okay, the cause of this seems to be that the CFbot currently uses "git apply --3way", not "git am --3way". For some reason "git apply" fails to apply the patch while "git am" succeeds. I'll check this weekend if I can change the logic to use "git am" instead.