- Original Message -
> From: "Daniel Axtens"
> To: "Veronika Kabatova" , "Stephen Finucane"
>
> Cc: patchwork@lists.ozlabs.org
> Sent: Tuesday, February 13, 2018 12:36:37 PM
> Subject: Re: [PATCH v2] Avoid timezone confusion
>
> Ve
Veronika Kabatova writes:
> - Original Message -
>> From: "Stephen Finucane"
>> To: vkaba...@redhat.com, patchwork@lists.ozlabs.org
>> Sent: Wednesday, January 17, 2018 8:22:27 PM
>> Subject: Re: [PATCH v2] Avoid timezone confusion
>>
&g
- Original Message -
> From: "Stephen Finucane"
> To: vkaba...@redhat.com, patchwork@lists.ozlabs.org
> Sent: Wednesday, January 17, 2018 8:22:27 PM
> Subject: Re: [PATCH v2] Avoid timezone confusion
>
> On Wed, 2018-01-17 at 19:18 +, Stephen Finucane w
On Wed, 2018-01-17 at 19:18 +, Stephen Finucane wrote:
> On Tue, 2018-01-16 at 18:58 +0100, vkaba...@redhat.com wrote:
> > From: Veronika Kabatova
> >
> > Patchwork saves patches, comments etc with UTC timezone and reports
> > this time when opening the patch details. However, internally
> >
On Tue, 2018-01-16 at 18:58 +0100, vkaba...@redhat.com wrote:
> From: Veronika Kabatova
>
> Patchwork saves patches, comments etc with UTC timezone and reports
> this time when opening the patch details. However, internally generated
> processes such as events are reported with the instance's loc
From: Veronika Kabatova
Patchwork saves patches, comments etc with UTC timezone and reports
this time when opening the patch details. However, internally generated
processes such as events are reported with the instance's local time.
There's nothing wrong with that and making PW timezone-aware wo
