On Tue, 1 Jul 2014 10:38:01 -0400, Bob Eby wrote: > Today, I set my clock back to May for some local web-server testing on > my dev box. > > While my clock was set back, my boss mentioned a change he pushed up > so I went to update and look at his change. To my surprise, his > change didn't show up in my change graph. Oddly enough, when my clock > reset itself about 20 minutes later to the correct time. I looked > again without any further pulls and there was his change, now visible > in the graph.
I guess it was because the client-side change detection uses file modification time. Did you restart TortoiseHg after system clock change or trigger refresh manually by F5 key? > If no one was looking for it when it happened, just how easy would it > be for an unruly developer to pre-post changes to an upstream > repository and make it look like those changes actually happened in > the future when they merely occurred in the present? > > Just wondering if this is a security hole and whether I should be > worried.. (or perhaps it's merely a display issue). No, push/pull protocol uses SHA1 hash. Commit date is just a meta data of changeset. Regards, ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
