> Keep in mind that git doesn't really CARE about timestamps to do most > operations; it operates on the graph created by parentage. Think of the > timestamps more as comments; when a commit is created, we comment who > did it and when, both accordinging to their local information. > > -Peff > > PS Nit: Git doesn't work with changesets, it works with snapshots, > building a directed graph of snapshots. Maybe that is the source of your > confusion It's true I don't know much about git, what is the difference between a changeset and a snapshot? Are you saying timestamps should be tracked separately or tracked by an scm system built on top of git? Does/should git care about the when of a snapshot? Perhaps my question is directed more toward gitweb.cgi, it seems to me the timestamp of when a snapshot was merged into this repository should somehow be tracked and that is what gitweb.cgi should default to display. For example, if someone wants to know if security bugfix X was merged into linus' kernel tree they also want to know when that happened, don't they? -Matt __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - 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