Re: Trivial fix for comment of function table_tuple_lock

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Trivial fix for comment of function table_tuple_lock
Date: 2025-09-23 00:51:29
Message-ID: 581FF43E-14A1-46CD-AA7B-F8632BDF39CD@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Sep 23, 2025, at 08:45, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
>
> I noticed the commit message in the patch lists you as "Author: Chao
> Li <lic(at)highgo(dot)com <mailto:lic(at)highgo(dot)com>>",
> but in this discussion you've been using "li(dot)evan(dot)chao(at)gmail(dot)com <mailto:li(dot)evan(dot)chao(at)gmail(dot)com>",
> which also seems to be the address used in past commit logs for you.
> Which email address would you like me to use in the commit log?
>

Please use lic(at)highgo(dot)com that is my company email address. Because the company email address doesn’t work well with Mail Archive, so I use my Gmail for daily community communications.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-09-23 01:01:54 Re: Fix overflow of nbatch
Previous Message Fujii Masao 2025-09-23 00:45:18 Re: Trivial fix for comment of function table_tuple_lock