Date: Wed, 7 Aug 2024 12:15:19 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Robert Haas <robertmhaas@gmail.com>,
	Alexander Korotkov <aekorotkov@gmail.com>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Introduce hash_search_with_hash_value() function
Message-ID: <ZrOrp-8TU_FtHA6D@nathan>
References: 
 <CA+TgmoaxUist2vuFZ6ofzDcuNcuxVgvN0p3-WYthw9zxyDrqPQ@mail.gmail.com>
 <202408071708.x3p2fbmwyb2u@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <202408071708.x3p2fbmwyb2u@alvherre.pgsql>
Archived-At: <https://www.postgresql.org/message-id/ZrOrp-8TU_FtHA6D%40nathan>
Precedence: bulk

On Wed, Aug 07, 2024 at 01:08:35PM -0400, Alvaro Herrera wrote:
> On 2024-Aug-07, Robert Haas wrote:
>> I really wish there was some way to fix commit messages. I had a typo
>> in mine today, too.
> 
> We could use git notes.  The UI is a bit inconvenient (they have to be
> pushed and pulled separately from commits), but they seem useful enough.

Yeah, I spend a lot of time on commit messages because they're pretty much
written in stone once pushed.  I'd definitely use git notes to add errata,
follow-up commits that fixed/reverted things, etc.

-- 
nathan