hellvee at gmail.com
Thu Oct 6 20:09:12 EDT 2016
I sure did if that was the point that you were trying to convey :-)
I simply thought that you'd missed the earlier reply that it was a GnuCash
Issue and reverting to the previous version had resolved the issue. I also
assumed that you were still trying to assist Keith debug the issue and was
really just attempting to answer your "Or are you telling us that all the
other places which display date/time are getting the change right but that
gnucash isn't?" question.
Cheers Dave H.
On 7 October 2016 at 09:23, Mike or Penny Novack <mpnovack at mtdata.com>
> On 10/6/2016 6:07 PM, Dave H wrote:
> It's already been confirmed it's an issue with timezone handling in
> 2.6.14, Keith reverted to 2.6.13 for now which fixed the issue.
> Cheers Dave H.
> You missed the point. I was suggesting how to look at something like this
> BEFORE coming to the list. In other words, if it affected all applications
> then you don't suspect a gnucash problem but something more global. But if
> it affects just gnucash with the other applications getting the date right,
> then must be a gnucash problem. That was important information to supply
> along with the question about the problem.
More information about the gnucash-user