Done. Thanks!
On Tue, May 5, 2020 at 11:47 AM Dave Barnes wrote:
> +1
> Go ahead, Jinmei, and cherry-pick the GEODE-8055 fix to the Geode
> support/1.13 branch.
>
> Dave
> Geode 1.13 release manager
>
>
> On Mon, May 4, 2020 at 10:12 PM Dick Cavender
> wrote:
>
> > +1
> >
> > On Mon, May 4, 202
+1
Go ahead, Jinmei, and cherry-pick the GEODE-8055 fix to the Geode
support/1.13 branch.
Dave
Geode 1.13 release manager
On Mon, May 4, 2020 at 10:12 PM Dick Cavender wrote:
> +1
>
> On Mon, May 4, 2020 at 8:28 PM Owen Nichols wrote:
>
> > Hi Jinmei, it looks like your commit came in just mi
+1
On Mon, May 4, 2020 at 8:28 PM Owen Nichols wrote:
> Hi Jinmei, it looks like your commit came in just minutes after the
> support/1.13 branch was cut, but before the email announcing the branch cut
> was sent. +1 from me to go ahead and bring to support/1.13 on that basis.
>
> > On May 4, 2
Hi Jinmei, it looks like your commit came in just minutes after the
support/1.13 branch was cut, but before the email announcing the branch cut was
sent. +1 from me to go ahead and bring to support/1.13 on that basis.
> On May 4, 2020, at 7:43 PM, Jinmei Liao wrote:
>
> Yes, there is a user r
Yes, there is a user request to reinstate this feature.
On Mon, May 4, 2020 at 4:41 PM Anilkumar Gingade
wrote:
> Since this issue is introduced from 1.7; meaning its present from 1.7 time,
> can it be added in the next release, is there any strong user/customer
> requirement to get this in 1.13
Since this issue is introduced from 1.7; meaning its present from 1.7 time,
can it be added in the next release, is there any strong user/customer
requirement to get this in 1.13.
-Anil.
On Mon, May 4, 2020 at 11:55 AM Jinmei Liao wrote:
> I would like to include the fix for GEODE-8055 in the
