Hi Stephen,
Thank you so much for such a detailed investigation! Very glad to hear
patchwork is doing the right things.
Regards,
Daniel
> On Thu, 2017-06-22 at 11:16 +0100, Stephen Finucane wrote:
>> On Thu, 2017-06-22 at 09:05 +1000, Daniel Axtens wrote:
>> > Hi Stephen,
>> >
>> > > Thanks
On Thu, 2017-06-22 at 11:16 +0100, Stephen Finucane wrote:
> However, despite this, Patchwork seems to managing just fine. There's only
> one patch out of series, and that's the one that has been sent as 1/2
> mistakenly. I don't know why this didn't get lumped into the existing series
> but it's
On Thu, 2017-06-22 at 11:16 +0100, Stephen Finucane wrote:
> On Thu, 2017-06-22 at 09:05 +1000, Daniel Axtens wrote:
> > Hi Stephen,
> >
> > > Thanks for doing this. I've tinkered with both instances and haven't seen
> > > any
> > > serious issues. I'm most happy with the fact that the
On Thu, 2017-06-22 at 09:05 +1000, Daniel Axtens wrote:
> Hi Stephen,
>
> > Thanks for doing this. I've tinkered with both instances and haven't seen
> > any
> > serious issues. I'm most happy with the fact that the performance of the
> > web UI
> > hasn't been altered (at least, from my brief
Hi Stephen,
> Thanks for doing this. I've tinkered with both instances and haven't seen any
> serious issues. I'm most happy with the fact that the performance of the web
> UI
> hasn't been altered (at least, from my brief testing).
>
> I'm thinking we give this another day or two and we might
On Wed, 2017-06-21 at 00:16 +1000, Daniel Axtens wrote:
> Hi all,
>
> I am running tests of v1 to v2 migrations. The origin is
> v1.patchwork.dja.id.au and the destination is
> migrate.patchwork.dja.id.au.
>
> Every hour, data is synced from 'v1' to 'migrate' - emails are only
> ingested in v1.
