Matthew L Foster wrote:
Sorry to bring up the time issue again [that I am perhaps still confused about] but I have been playing around with git more and I think I can phrase my question/observation better. From viewing gitweb.cgi I have observed a situation where Linus creates a tag, say rc1, and then he later merges changes but some subset of those changes/commits show up in the list in time order as taking place _before_ the rc1 tag was made even though they were merged after. Do I describe a real or possible phenomenon? And does this happen because the developer that made the subset of changes in question commit them to his/her local repository in time order before the rc1 tag was made? So an external repository had the change before the rc1 tag was made but Linus' repository didn't? But internally git on Linus' machine knows that the gitweb.cgi displayed time order is wrong as far as the state is concerned because each repository's index file keeps local track of the true local state [just time isn't reconcilable], or am I missing something(s)? Is it possible for gitweb.cgi to have a new view mode that sorts/displays the list based on merge time for commits (the time merged into Linus' or whatever repository) so the above situation doesn't happen? The actual time of a local commit should be the time it was merged locally not the time it was created externally/originally, right? Where can I find the gitweb.cgi source/package? I could maybe hack gitweb.cgi myself. Please CC me on any replies since I am not subscribed to the list. -Matt
The last time this topic came up, folks either created (or pointed to) reflogs as a way to determine the changes to the local state of a repo.
i.e. by checking the reflog for a ref, you could say that that ref was changed from v2.6.20 to v2.6.21 at such and such date and time.
That would allow you to determine what commits were available via that ref at a particular time, regardless of the actual commit dates.
To the best of my knowledge, though, reflogs are not enabled by default on bare repos, and gitweb makes no use of the reflogs anyway.
Rogan - 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
