--- Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> The point is, there is no "locally".
>
> Do you mean locally on my machine? That's actually *different* from the
> locally on the public machines, and no, I wouldn't give you that
> information anyway (since that information would include the mistakes that
> I fixed up ;)
Ok that explains it. How about locally on gitX.kernel.org [would have to be real git repository]?
I'd want gitweb.cgi running on my local repository to use the local time of local merges to ensure
the problem I described at the start of this thread doesn't happen. Git reset --hard can be used
to fix mistakes and that wouldn't show?
> And in fact, even on the public machines, the "locally" would be different
> depending on things like mirroring delays
Yes, it should be different, everyone's local commit/merge order is not the same.
> So in theory, we could pick one particular public kernel.org machine, and
> use the times as _that_ machine sees it, but the fact is, that isn't how
> git works. No normal git command will ever show you such a senseless
> ordering.
Is local commit order really senseless? Using local commit order and/or the local time of local
merges would solve the problem I mentioned in the start of this thread? I don't think this info
has to be exported to CVS, a web interface to git and/or git itself should be able to tell us what
local time order and/or what local commit order merges were made in.
-Matt
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
