{"thread":{"id":"26314","subject":"impact on git of changing linux o/s system-date frequently","startedAt":"2011-01-21T00:01:10Z","lastAt":"2011-01-21T07:13:15Z","messageCount":2,"participants":["Neal Kreitzinger","David Brown"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"159724","messageId":"ihaie3$63g$1@dough.gmane.org","threadId":"26314","inReplyTo":null,"subject":"impact on git of changing linux o/s system-date frequently","fromName":"Neal Kreitzinger","fromEmail":"neal@rsss.com","sentAt":"2011-01-21T00:01:10Z","receivedAt":"2011-01-21T00:01:10Z","isPatch":false,"sender":{"key":"neal@rsss.com","avatar":null},"body":"What are the implications of linux o/s system-date changes on git?\n\nWe plan on having test VM's on which the linux o/s system-date (linux \"date\" \ncommand) is changed several times to test time lapse scenarios, e.g. go \nforward 30 days in the future.  We use git to pull updates from the \ndevelopment machine to mirror repos and cloned repos on the test VM, and to \ncreate test areas (local repos) on the test VM.  We do not use git-push or \ngit-commit on the test VM at this time.\n\nv/r,\nNeal \n"},{"id":"159734","messageId":"8yaaaiuhgqc.fsf@huya.qualcomm.com","threadId":"26314","inReplyTo":"ihaie3$63g$1@dough.gmane.org","subject":"Re: impact on git of changing linux o/s system-date frequently","fromName":"David Brown","fromEmail":"davidb@codeaurora.org","sentAt":"2011-01-21T07:13:15Z","receivedAt":"2011-01-21T07:13:15Z","isPatch":false,"sender":{"key":"davidb@codeaurora.org","avatar":"https://gravatar.com/avatar/1bacedec21621bd4efa4bc8ecb05c507f0cf0641ecdaa50943c2ed21c8ef22d8?d=mp&s=160"},"body":"On Thu, Jan 20 2011, Neal Kreitzinger wrote:\n\n> What are the implications of linux o/s system-date changes on git?\n>\n> We plan on having test VM's on which the linux o/s system-date (linux \"date\" \n> command) is changed several times to test time lapse scenarios, e.g. go \n> forward 30 days in the future.  We use git to pull updates from the \n> development machine to mirror repos and cloned repos on the test VM, and to \n> create test areas (local repos) on the test VM.  We do not use git-push or \n> git-commit on the test VM at this time.\n\nWithout making commits on the machine, there won't be any history being\ncreated with misordered dates, so there shouldn't be any issues there.\n\nThe index should also be pretty resiliant to time warping as well, and\nif you aren't modifying any of the git managed files, I don't think you\ncan provoke anything.\n\nIf you're doing edits of files, there's a slight possibility the edited\nversion could end up with the same ctime/mtime as the cache in the\nindex, and git would miss the change.  Again, it doesn't sound like you\nare doing this.\n\nDavid\n\n-- \nSent by an employee of the Qualcomm Innovation Center, Inc.\nThe Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.\n"}]}