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 1tqVGv-005uzB-S8 for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Mar 2025 10:49:42 +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 1tqVGt-00GRDK-Vy for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Mar 2025 10:49:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tqVGt-00GRDC-Ic for pgsql-hackers@lists.postgresql.org; Fri, 07 Mar 2025 10:49:39 +0000 Received: from mail-lf1-x12f.google.com ([2a00:1450:4864:20::12f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tqVGp-001U4T-2K for pgsql-hackers@lists.postgresql.org; Fri, 07 Mar 2025 10:49:38 +0000 Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-548409cd2a8so1644500e87.3 for ; Fri, 07 Mar 2025 02:49:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeltef.nl; s=google; t=1741344576; x=1741949376; 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=2736x54ulDUNSMWsR+vyEIVXaeTxgf/a9jJsA4l5FPM=; b=B4ShpepZOd3tM3U2A1eCCPZF4EbwhQRI2PIOPtkRMuoBE1ogQumT6k/XJDMkl2vlS1 wriROeiGQwYKs1qWoF3RFENky11WAYSPmt5jYszWpDuRjtQo4Q6k3HvZECKXjnvktqZe PmwyI8wGZS7SpquAUSCGwKKKUt0M+AQ1EQJDNR8QNb7quKVr/aWmybi09wKQV1+wZo1u G0FDIskPnv4VHkXuboJRCLF0sjOXSP3CNLel5nL6SLgN7diQmZZk4NkSZgSmLaGTu2DP nT3b5l22klNfiZc92QYYJ7M2Chq1rQajsDS2e6/5AP91wW5gllp67ZHbMHxLnS007lbD erzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741344576; x=1741949376; 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=2736x54ulDUNSMWsR+vyEIVXaeTxgf/a9jJsA4l5FPM=; b=hJrdltc2fPKhehPIx5c9J3J2G8srLTJeeuACMSv8+Vbeldwr1QgjzP6QPgMatNMeHx VGV3rv7blxOLS9RsD52hphc7XrsCr1h7nKpTHbHKz51Q5g03vRjw7SevzqIZ5bBm4nm7 KDzn1lvypXTskILd2MIZ5EtY5Y8OIVQCXXvlmgtEeVf99EVM/8Qm6YrRbR8wiiZQxJTN z5b9yJpdapDGu7kKHfzvaptIk9A10vjNtJdrXOjJkZbDqwIwmukvSmzarni2HcV6nk+w FOnFJBokNm4iGyqUsdEUEKwBzROJspNrgapMW1IiBmDmR3rRy8rrqeFtPxso0FzDvDU0 I+5g== X-Gm-Message-State: AOJu0Yx84SDAqeWQsmkKnbpwYXdiHJVxshLL94SsIxPRK2QeRSwIusCT 1HOyYSQ0KewVZXlpxBiJMgkOOLheuM6g5g/BHcOyk3iA7OMpDUkcceEAxfuV5BxHyRWF7ADJKxL 7XoJwPtdAMgEPojgitSixm9aGlzVRN4AvmUAxKRFYKZyDBFHFN7k= X-Gm-Gg: ASbGncux88YEKc11+Jl8TYKCqCPdbg6b7p1M0aqbPucnZRCkVAC1isEl/ASFZsbxi9n s2/UhPRqjLWmJaPw+IhBQmgPJAUGxAidfss0erRIVJUXIETBFYuRbUDkmhuekVpdPTh2znW3PwK fy8zyUiA5A8TTzEHYsAP1gHb37Pe0= X-Google-Smtp-Source: AGHT+IExaYZJrr2bdNjOAQ6AngOsYYbu4x+NlDVxUkNzCYASgid+al651pswgLPlYC4ccPrOjX1xtvp+ApwTV4Zp+mA= X-Received: by 2002:a05:6512:3e1a:b0:545:c9d:ef26 with SMTP id 2adb3069b0e04-54990ec8c65mr875432e87.46.1741344575514; Fri, 07 Mar 2025 02:49:35 -0800 (PST) MIME-Version: 1.0 References: <703819.1741281033@sss.pgh.pa.us> In-Reply-To: From: Jelte Fennema-Nio Date: Fri, 7 Mar 2025 11:49:23 +0100 X-Gm-Features: AQ5f1Joyu6SBjlqIq1r2YaxlzL2zkzwlnNZ5WWCOZwjj-Kfi-3eqOYIFC2tP0U0 Message-ID: Subject: Re: Commitfest app release on Feb 17 with many improvements To: Andreas Karlsson Cc: pgsql-hackers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 7 Mar 2025 at 11:26, Andreas Karlsson wrote: > Out of curiosity: do you track which method works? I would expect > everything to be applied with either git am or patch which can be > applied with git apply making git apply technically unnecessary. I think we need all of them... - git apply is unable to apply the patch in 5272 on top of main - git am, works with that 5272, but cannot apply any patch not created by git format-patch (for instance 5522) - I've been unable to get patch(1) not to return a failure if the patch is already applied. So applying e.g. 5522 twice. git apply handles that fine.