David Lang <dlang@xxxxxxxxxxxxxxxxxx> writes: >>> remember that a pach could be merged to many trees in any order. which >>> merge date do you want to know about? >> >> The date that repository I am looking at with gitweb first had >> that commit, of course. What other dates did you have in mind? > > if that repository is then merged into another one, what date would > that second one record for that commit? the date it was pulled there? > > in many cases this would seem to be useless or distracting information > (you already display where in the history the merge took place, do you > really need to attach that date to all changes that arrive from the > branch?) Usually, but not on fast forward. Only when somebody is interested in the particular question "when did this commit has become part of this branch" it becomes relevant. And do not get me wrong. I am in principle agreeing with you that this is an extra information for most of the time -- I even doubt "when did this commit has become part of this branch" is all that useful. - 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