date problem ?

Added by Richard PALO over 3 years ago

Perhaps it's the developers pushing ahead of schedule !
In the clip attached, I'm surprised to see revision 13182 "already" committed - tomorrow

Capture-6.png (75.9 kB)


Replies (3)

RE: date problem ? - Added by Jeppe Toustrup over 3 years ago

It could seem like the time on Garrett's machine is a bit ahead of time :)

RE: date problem ? - Added by Richard PALO about 2 years ago

Looks like the "time warp" is back ...

Capture-1.png (98.5 kB)

RE: date problem ? - Added by Jeppe Toustrup about 2 years ago

I'm not so sure about that being a problem. It may just be the nature of a distributed file system, in case Richard committed something on a local branch a while ago, but didn't push it to the central repository until now, it will look like that in the overview.

Edit: Actually, I can see this from the IRC log for last night:

<CIA-20> illumos Richard Lowe <richlowe@richlowe.net>: 2022 libnisdb mis-compares strings Reviewed by: Robert Mustacchi <rm@joyent.com> Reviewed by: Garrett D'Amore <garrett@damore.org> Reviewed by: Joshua M. Clulow <josh@sysmgr.org> Approved by: Gordon Ross <gwr@nexenta.com>
<CIA-20> illumos Richard Lowe <richlowe@richlowe.net>: 2023 libnisdb is inconsistently const-y Reviewed by: Robert Mustacchi <rm@joyent.com> Reviewed by: Garrett D'Amore <garrett@damore.org> Reviewed by: Joshua M. Clulow <josh@sysmgr.org> Approved by: Gordon Ross <gwr@nexenta.com>
<CIA-20> illumos Richard Lowe <richlowe@richlowe.net>: 2018 makedbm overwrites and overflows constant string Reviewed by: Robert Mustacchi <rm@joyent.com> Reviewed by: Garrett D'Amore <garrett@damore.org> Reviewed by: Joshua M. Clulow <josh@sysmgr.org> Approved by: Gordon Ross  <gwr@nexenta.com>
<jeffpc> why do soe of those commits appear as 8 months ago?
<richlowe> Because they're 8 months old.
<jeffpc> oh
<jeffpc> is there a giant backlog?
<richlowe> of my changes?  Sort of.

(1-3/3)