node.c: Fix incorrect timestamp order when parsing long values.
The timestamps are in the Write/Change/Access order, not the NT API order Access/Write/Change. The incorrect order was only for the values returned to the visitor, not for the printout itself which was correct. This should fix github issue #22.
E
Erik Larsson committed
53b2fc24f883de92e1538c93af9c21d681dc446c
Parent: 0b15365