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.96) (envelope-from ) id 1wuBKg-000WDo-0Q for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Aug 2026 15:57:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wuBKd-008pqH-2u for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Aug 2026 15:57:33 +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.96) (envelope-from ) id 1wuBKd-008pq8-1z for pgsql-hackers@lists.postgresql.org; Wed, 12 Aug 2026 15:57:32 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wuBKc-00000000NlW-0Vv1 for pgsql-hackers@lists.postgresql.org; Wed, 12 Aug 2026 15:57:32 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 67CFvRYg2730905; Wed, 12 Aug 2026 11:57:27 -0400 From: Tom Lane To: Corey Huinker cc: Etsuro Fujita , pgsql-hackers@lists.postgresql.org Subject: Re: Credits For v19 In-reply-to: References: Comments: In-reply-to Corey Huinker message dated "Wed, 12 Aug 2026 11:53:35 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2730903.1786550247.1@sss.pgh.pa.us> Date: Wed, 12 Aug 2026 11:57:27 -0400 Message-ID: <2730904.1786550247@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Corey Huinker writes: > I'm going to use an abundance of caution here and ask whether > "given-name-first" order is the correct order we should be using for them > in the credits. As much as I might think I might know the correct answer, I > want to be sure. Yes, I believe that's the consensus about how to do this. regards, tom lane