{"thread":{"id":"5739","subject":"Re: git and time","startedAt":"2006-09-28T17:30:51Z","lastAt":"2006-09-28T17:30:51Z","messageCount":1,"participants":["Matthew L Foster"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"27910","messageId":"20060928173051.94640.qmail@web51004.mail.yahoo.com","threadId":"5739","inReplyTo":"20060928170110.GD3650@socrates.priv","subject":"Re: git and time","fromName":"Matthew L Foster","fromEmail":"mfoster167@yahoo.com","sentAt":"2006-09-28T17:30:51Z","receivedAt":"2006-09-28T17:30:51Z","isPatch":false,"sender":{"key":"mfoster167@yahoo.com","avatar":null},"body":"--- Tom Prince wrote:\n\n> On Thu, Sep 28, 2006 at 09:55:08AM -0700, Matthew L Foster wrote:\n> > \n> > --- Rogan Dawes wrote:\n> > \n> > > I just don't think that any of the kernel developers feel the need to \n> > > police any one else's clocks . . . they're more interested in the \n> > > contents of the patch.\n> > \n> > I am not saying git should \"police any one else's clocks\", I am saying git should be designed\n> or\n> > configured in such a way, using local time, that it obviates the current reliance on everyone\n> > else's clock being set correctly. \n> > \n> > -Matt\n> \n> The point is, it DOES NOT rely on anyone's clock being set correctly.\n\ngitweb.cgi does. It should be possible to export git data, through say a web interface, in a such\na way that local time order is consistent with commit order. \n\n[responding to Linus' mail here:] I understand that git doesn't care about time internally as it\ntreats it as a random number for people to care about or not on their own, I am only saying that\nlocal time is more likely to be cared about than disparate remote creation times. \n\n-Matt\n\n\n__________________________________________________\nDo You Yahoo!?\nTired of spam? Yahoo! Mail has the best spam protection around \nhttp://mail.yahoo.com \n"}]}