Re: API stability

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: robertmhaas(at)gmail(dot)com
Cc: michael(at)paquier(dot)xyz, tgl(at)sss(dot)pgh(dot)pa(dot)us, markus(dot)wanner(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: API stability
Date: 2022-04-11 04:29:55
Message-ID: 20220411.132955.60754403387952021.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

(a bit off-topic)

I'm not sure where I am..

At Wed, 06 Apr 2022 10:36:30 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
me> > this if nobody else would like to do it, but let me ask whether
me> > Kyotaro Horiguchi would like to propose a patch, since the original
me> > patch did, and/or whether you would like to propose a patch, as the
me> > person reporting the issue.
me>
me> I'd like to do that. Let me see.

At Thu, 7 Apr 2022 10:04:20 -0400, Robert Haas <robertmhaas(at)gmail(dot)com> wrote in
> struct, which is what we now need to fix. Since I don't hear anyone
> else volunteering to take care of that, I'll go work on it.

Just confirmation. Is my message above didn't look like declaring that
I'd like to volunteering? If so, please teach me the correct way to
say that, since I don't want to repeat the same mistake. Or are there
some other reasons? (Sorry if this looks like a blame, but I asking
plainly (really:).)

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2022-04-11 05:39:53 pgsql: Put new command-line options into alphabetical order in help out
Previous Message Michael Paquier 2022-04-11 00:55:21 pgsql: doc: Clarify behavior of query planner locking with REINDEX

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-04-11 04:39:30 Re: typos
Previous Message Richard Guo 2022-04-11 04:25:28 Re: MERGE bug report