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 1s65Cc-009zWP-P5 for pgsql-hackers@arkaria.postgresql.org; Sun, 12 May 2024 09:09:06 +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 1s65CY-00A1J8-Pt for pgsql-hackers@arkaria.postgresql.org; Sun, 12 May 2024 09:09:03 +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 1s65CY-00A1J0-Dc for pgsql-hackers@lists.postgresql.org; Sun, 12 May 2024 09:09:02 +0000 Received: from mail-pg1-x535.google.com ([2607:f8b0:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s65CW-000dcv-3x for pgsql-hackers@postgresql.org; Sun, 12 May 2024 09:09:02 +0000 Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-6333b2551ebso2304864a12.0 for ; Sun, 12 May 2024 02:09:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715504938; x=1716109738; darn=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=Pn6uH2KwPwIJYab9CTn3cvYOZUJra3veQtDx4cX5Dnw=; b=DFa7XBrAoHjgiHxgWIDL67VPj9B27x7+hwRqbaiQz418TB62bRTLSIk30aqsfwAfms VsFhTupxjIZlXre2vxZrMqfljexLx293Se+CjftOYzcWPNH+Nd6Bzl+5S8bqczHsYXLG +LQApk9i0kPe64CAXJyjfgZIVJ1UtIjUGYxLowUl4vvib2vnHszP2qatIszxkXT1yRy7 Of1lcMoS0e/m4r0CyqAIAVYjeUHMTkWf/R45BXTjm3CdkLhWOu0iMGcJdS3kmZ0/S8uA 6kPzm8zX5ki0r5kpAl8XOcoOa3lDBlt7UWOESFBOx4rbHUOPLlmrlvXvlmTFY1A3wKK5 PpqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715504938; x=1716109738; 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=Pn6uH2KwPwIJYab9CTn3cvYOZUJra3veQtDx4cX5Dnw=; b=hjhUokIM2wNBZ1q5BQSpIyeMM4rnLFm/0Xq/QcUA28lmfATv0PAGfVcWCFlwX2Drsa eLyvt11R/dAtNso8Pc6ZBmp2wEvIeJb9NfYxSWZsUjGRZxfQ2u7ZA2fo5GZhUpZxGTvu tWW1D5lEcsUgz2C74GKiLUfcGvKs4CF5bcOHy5DxC1cvZqQwqjQSZtREixZXhJnGElGb FQ2gfkrgj6CaCo96cIEWmw/9+cgWJGdFsxX7NDqHpzTgpW4Klca70OTDQEPedOIgOwzW azkZ4aKf64wkjm1hplABlJs7JmsVNE7MxoZM24ZticCwbhq0qBknQ4vAIeOK03cgGEPm FfnA== X-Gm-Message-State: AOJu0Yy7ofuzsdFqArXEZ8ViuwbvgGom2CATuss+KKuBIfC79VuACf9t 3YWjpwXJS1O0BbtDpyppk9fQgrp2rf/j4HUal/xbQJuzg6BjyCjCGIxxK2biV0t5s1ldP1nVyUa oKaGKJb7zaoItr8t7iFYm5fzdLvp5onGB X-Google-Smtp-Source: AGHT+IFgTQEunNKl+smpNuAY2pjuV8KDfsQCqIn/jGNo8uZXIrDGz+pt7bEk8SwNeHOKoHhq9zrnCAOxtgC2JBB4M/E= X-Received: by 2002:a17:90a:af86:b0:2b5:91d1:3ae8 with SMTP id 98e67ed59e1d1-2b6c711009cmr10986617a91.14.1715504938252; Sun, 12 May 2024 02:08:58 -0700 (PDT) MIME-Version: 1.0 References: <20240512.155006.1316723460000187647.t-ishii@sranhm.sra.co.jp> In-Reply-To: <20240512.155006.1316723460000187647.t-ishii@sranhm.sra.co.jp> From: Nazir Bilal Yavuz Date: Sun, 12 May 2024 12:08:47 +0300 Message-ID: Subject: Re: CFbot does not recognize patch contents To: Tatsuo Ishii Cc: pgsql-hackers@postgresql.org, Thomas Munro Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Sun, 12 May 2024 at 09:50, Tatsuo Ishii wrote: > > After sending out my v18 patches: > https://www.postgresql.org/message-id/20240511.162307.2246647987352188848.t-ishii%40sranhm.sra.co.jp > > CFbot complains that the patch was broken: > http://cfbot.cputube.org/patch_48_4460.log > > === Applying patches on top of PostgreSQL commit ID 31e8f4e619d9b5856fa2bd5713cb1e2e170a9c7d === > === applying patch ./v18-0001-Row-pattern-recognition-patch-for-raw-parser.patch > gpatch: **** Only garbage was found in the patch input. > > The patch was generated by git-format-patch (same as previous > patches). I failed to find any patch format problem in the > patch. Does anybody know what's wrong here? I am able to apply all your patches. I found that a similar thing happened before [0] and I guess your case is similar. Adding Thomas to CC, he may be able to help more. Nitpick: There is a trailing space warning while applying one of your patches: Applying: Row pattern recognition patch (docs). .git/rebase-apply/patch:81: trailing whitespace. company | tdate | price | first_value | max | count [0] postgr.es/m/CA%2BhUKGLiY1e%2B1%3DpB7hXJOyGj1dJOfgde%2BHmiSnv3gDKayUFJMA%40mail.gmail.com -- Regards, Nazir Bilal Yavuz Microsoft