git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git and time

From
Nicolas Pitre <nico@cam.org>
Date
Sep 28, 2006, 03:07 UTC
Message-ID
<Pine.LNX.4.64.0609272252041.9349@xanadu.home>
In-Reply-To
<7vzmck7pis.fsf@assigned-by-dhcp.cox.net>
On Wed, 27 Sep 2006, Junio C Hamano wrote:
Show 18 quoted lines
> As Shawn said in a nearby thread, in a public and prominent
> repository like kernel.org repository it may sometimes be
> interesting and useful to know when each commit became available
> on each branch.  I am reasonably sure that it would not however
> make gitweb output easier to read to order its output by that
> timestamp.   Linus pulls from subsystem maintainers all the time
> and one pull may bring in dozens of commits, and they will get
> the same timestamp if you did so.  Actually it is worse than
> that.  He tends to batch, so he would have many such pulls and
> patch applications in his private repository, perhaps over a few
> hour, but the result will be pushed out to kernel.org with one
> push operation.  To show the "truthful" time, your gitweb would
> give the timestamp of that push operation for hundreds of
> commits pushed out during that operation.
> 
> I do not personally think that would be useful at all.  And I
> happen to know how expensive to teach gitweb to produce such an
> output, so I would not seriously suggest anybody to try it.

I beg to differ. Such information might be really useful. I agree though that this is an expensive operation and gitweb might not be the best place for it at all.

For example... some times I look at git-log output and finds about a certain bug fix that was apparently committed a month ago. And incidentally I recall having been bitten by that bug not really long ago, say last week. Although the bug fix was committed _somewhere_ last month, what I would really want to know is just when _i_ received that bug fix in my own repository to determine if it was before or after last week. So if it was before last week then I could conclude that the bug fix didn't actually fix my bug. Knowing that it has been committed last month is absolutely useless to me in this case.

Nicolas
Previous: Tom PrinceNext: Tom Prince
Message 46 of 115 in “git and time”
  1. Matthew L FosterSep 26, 2006
  2. Johannes SchindelinSep 26, 2006
  3. Jakub NarebskiSep 26, 2006
  4. Jeff KingSep 26, 2006
  5. Matthew L FosterSep 27, 2006
  6. SeanSep 27, 2006
  7. David LangSep 27, 2006
  8. SeanSep 27, 2006
  9. Junio C HamanoSep 27, 2006
  10. David LangSep 27, 2006
  11. SeanSep 27, 2006
  12. Junio C HamanoSep 27, 2006
  13. SeanSep 27, 2006
  14. Junio C HamanoSep 27, 2006
  15. Andreas EricssonSep 27, 2006
  16. Jeff KingSep 27, 2006
  17. Matthew L FosterSep 27, 2006
  18. Andreas EricssonSep 27, 2006
  19. Matthew L FosterSep 27, 2006
  20. Linus TorvaldsSep 27, 2006
  21. Matthew L FosterSep 27, 2006
  22. Linus TorvaldsSep 27, 2006
  23. Matthew L FosterSep 27, 2006
  24. Linus TorvaldsSep 27, 2006
  25. Matthew L FosterSep 27, 2006
  26. Linus TorvaldsSep 27, 2006
  27. Matthew L FosterSep 27, 2006
  28. Linus TorvaldsSep 27, 2006
  29. Shawn PearceSep 27, 2006
  30. Linus TorvaldsSep 27, 2006
  31. Matthew L FosterSep 28, 2006
  32. Jeff KingSep 28, 2006
  33. Shawn PearceSep 28, 2006
  34. Matthew L FosterSep 28, 2006
  35. Linus TorvaldsSep 28, 2006
  36. Andreas EricssonSep 29, 2006
  37. Johannes SchindelinSep 29, 2006
  38. Andreas EricssonSep 29, 2006
  39. Junio C HamanoSep 28, 2006
  40. Matthew L FosterSep 28, 2006
  41. SeanSep 28, 2006
  42. Matthew L FosterSep 28, 2006
  43. David LangSep 28, 2006
  44. SeanSep 28, 2006
  45. Tom PrinceSep 28, 2006
  46. Nicolas PitreSep 28, 2006
  47. Tom PrinceSep 28, 2006
  48. Shawn PearceSep 28, 2006
  49. Junio C HamanoSep 28, 2006
  50. Theodore TsoSep 28, 2006
  51. Matthew L FosterSep 28, 2006
  52. Nicolas PitreSep 28, 2006
  53. Junio C HamanoSep 28, 2006
  54. Nicolas PitreSep 28, 2006
  55. Junio C HamanoSep 28, 2006
  56. Junio C HamanoSep 29, 2006
  57. Shawn PearceSep 30, 2006
  58. Junio C HamanoSep 30, 2006
  59. Linus TorvaldsSep 30, 2006
  60. Junio C HamanoSep 30, 2006
  61. Linus TorvaldsOct 1, 2006
  62. Junio C HamanoOct 1, 2006
  63. Junio C HamanoOct 1, 2006
  64. Johannes SchindelinOct 1, 2006
  65. Jakub NarebskiOct 2, 2006
  66. Jakub NarebskiSep 29, 2006
  67. Shawn PearceSep 27, 2006
  68. Matthew L FosterSep 27, 2006
  69. Shawn PearceSep 27, 2006
  70. Andy WhitcroftSep 27, 2006
  71. Linus TorvaldsSep 27, 2006
  72. Edgar ToernigSep 27, 2006
  73. Linus TorvaldsSep 27, 2006
  74. Jakub NarebskiSep 29, 2006
  75. Linus TorvaldsSep 27, 2006
  76. Jakub NarebskiOct 3, 2006
  77. Jeff KingSep 27, 2006
  78. SeanSep 27, 2006
  79. Junio C HamanoSep 27, 2006
  80. SeanSep 27, 2006
  81. Shawn PearceSep 27, 2006
  82. Junio C HamanoSep 27, 2006
  83. Junio C HamanoSep 27, 2006
  84. Shawn PearceSep 27, 2006
  85. Junio C HamanoSep 27, 2006
  86. Shawn PearceSep 27, 2006
  87. Jeff KingSep 27, 2006
  88. SeanSep 27, 2006
  89. Theodore TsoSep 28, 2006
  90. Matthew L FosterSep 28, 2006
  91. Rogan DawesSep 28, 2006
  92. Matthew L FosterSep 28, 2006
  93. Linus TorvaldsSep 28, 2006
  94. Junio C HamanoSep 28, 2006
  95. Matthew L FosterSep 28, 2006
  96. Johannes SchindelinSep 28, 2006
  97. Matthew L FosterSep 28, 2006
  98. Shawn PearceSep 28, 2006
  99. Matthew L FosterSep 28, 2006
  100. Johannes SchindelinSep 28, 2006
  101. Matthew L FosterSep 28, 2006
  102. Andreas EricssonSep 29, 2006
  103. Linus TorvaldsSep 28, 2006
  104. Matthew L FosterSep 28, 2006
  105. Theodore TsoSep 29, 2006
  106. Matthew L FosterSep 29, 2006
  107. Junio C HamanoSep 29, 2006
  108. Robin RosenbergSep 28, 2006
  109. A Large Angry SCMSep 28, 2006
  110. Matthew L FosterSep 28, 2006
  111. A Large Angry SCMSep 28, 2006
  112. Matthew L FosterSep 28, 2006
  113. Matthew L FosterSep 28, 2006
  114. Jan HarkesSep 29, 2006
  115. SeanSep 29, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.