public inbox for [email protected]  

help / color / mirror / Atom feed

From: vignesh C <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Nikolay Shaplov <[email protected]>
Cc: [email protected]
Cc: Jeff Davis <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Amit Langote <[email protected]>
Cc: Ian Lawrence Barwick <[email protected]>
Subject: Re: [PATCH] New [relation] option engine
Date: Thu, 2 Feb 2023 08:33:46 +0530
Message-ID: <CALDaNm2KHa4kjqT3wab-K9BeZxEVQgfphOCSd3Mu4CF_iz6Srg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CALDaNm0OHMJSD=3RcB4Uvm8h-gEg+rrvj=A-g9_1XAbyKjG9RA@mail.gmail.com>
	<[email protected]>

On Wed, 1 Feb 2023 at 14:49, Alvaro Herrera <[email protected]> wrote:
>
> On 2023-Jan-31, vignesh C wrote:
>
> > On Tue, 3 Jan 2023 at 18:38, vignesh C <[email protected]> wrote:
>
> > > The patch does not apply on top of HEAD as in [1], please post a rebased patch:
> > > === Applying patches on top of PostgreSQL commit ID
> > > 92957ed98c5c565362ce665266132a7f08f6b0c0 ===
> > > === applying patch ./new_options_take_two_v03f.patch
> > > patching file src/include/access/reloptions.h
> > > Hunk #1 FAILED at 1.
> > > 1 out of 4 hunks FAILED -- saving rejects to file
> > > src/include/access/reloptions.h.rej
> >
> > There has been no updates on this thread for some time, so this has
> > been switched as Returned with Feedback. Feel free to open it in the
> > next commitfest if you plan to continue on this.
>
> Well, no feedback has been given, so I'm not sure this is a great
> outcome.  In the interest of keeping it alive, I've rebased it.  It
> turns out that the only conflict is with the 2022 -> 2023 copyright line
> update.
>
> I have not reviewed it.

Since there was no response to rebase the patch, I was not sure if the
author was planning to continue. Anyways Nikolay Shaplov plans to work
on this soon, So I have added this to the next commitfest at [1].
[1] - https://commitfest.postgresql.org/41/3536/

Regards,
Vignesh

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [PATCH] New [relation] option engine
  In-Reply-To: <CALDaNm2KHa4kjqT3wab-K9BeZxEVQgfphOCSd3Mu4CF_iz6Srg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox