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

Re: [PATCH] [RFD] Add repoid identifier to commit

From
Sean <seanlkml@sympatico.ca>
Date
May 11, 2005, 23:01 UTC
Message-ID
<2883.10.10.10.24.1115852463.squirrel@linux1>
In-Reply-To
<1115851718.22180.153.camel@tglx>
On Wed, May 11, 2005 6:48 pm, Thomas Gleixner said:
Hey Thomas,
Show 7 quoted lines
> Maybe you have missed the point, where one Committer holds more than one
> repository. See davem/net-2.6 and davem/sparc-2.6. Not to talk of
> Russell King's and Greg's multiple repositories.
> The Author is irrelevant, because one Author sends patches to more than
> one maintainer. Author _cannot_ be a source of tracking information. If
> you want to do heuristic guesses on Author/Committer pairs, then you
> make the situation more complex than it is already.

Why would anyone care how many repositories Russell or Greg use? Why does anyone care if Dave used his repo A, B, or C? Aren't I still just going to contact him via his author email addy if I have an issue with an object he has added to the stream?

And if I do care which repo he used, why don't I care about the case i've outlined where the chain of command information is lost?

> As I said before it is completely irrelevant whether fast forward was
> pulled into C directly from A or from B.
>
> Whats the relevant content of getting the same thing from A or B ?

Exactly!!! So what is relevant of getting the same thing from Dave's A or B? The only point would be to show chain of command, but you don't seem interested in that.

> If you want to do this, you break the fast forward mechanism and
> reinvent the pull ping-pong which is avoided by the fast forwards.
Yes, I think there are other ways to avoid the ping pong too.
Sean
Previous: Thomas GleixnerNext: Thomas Gleixner
Message 8 of 74 in “[RFD] Add repoid identifier to commit”
  1. [RFD] Add repoid identifier to commitThomas Gleixner, May 11, 2005
  2. SeanMay 11, 2005
  3. Thomas GleixnerMay 11, 2005
  4. SeanMay 11, 2005
  5. Thomas GleixnerMay 11, 2005
  6. SeanMay 11, 2005
  7. Thomas GleixnerMay 11, 2005
  8. SeanMay 11, 2005
  9. Thomas GleixnerMay 11, 2005
  10. SeanMay 11, 2005
  11. Thomas GleixnerMay 12, 2005
  12. SeanMay 12, 2005
  13. Thomas GleixnerMay 12, 2005
  14. SeanMay 12, 2005
  15. David WoodhouseMay 12, 2005
  16. SeanMay 12, 2005
  17. Thomas GleixnerMay 12, 2005
  18. David WoodhouseMay 12, 2005
  19. SeanMay 12, 2005
  20. SeanMay 12, 2005
  21. H. Peter AnvinMay 11, 2005
  22. Thomas GleixnerMay 11, 2005
  23. H. Peter AnvinMay 11, 2005
  24. SeanMay 11, 2005
  25. H. Peter AnvinMay 12, 2005
  26. SeanMay 12, 2005
  27. Thomas GleixnerMay 12, 2005
  28. Junio C HamanoMay 12, 2005
  29. Thomas GleixnerMay 12, 2005
  30. SeanMay 12, 2005
  31. Thomas GleixnerMay 12, 2005
  32. SeanMay 12, 2005
  33. Thomas GleixnerMay 12, 2005
  34. SeanMay 12, 2005
  35. Thomas GleixnerMay 12, 2005
  36. SeanMay 12, 2005
  37. Thomas GleixnerMay 12, 2005
  38. SeanMay 12, 2005
  39. Thomas GleixnerMay 12, 2005
  40. SeanMay 12, 2005
  41. SeanMay 12, 2005
  42. David WoodhouseMay 12, 2005
  43. SeanMay 12, 2005
  44. Jan HarkesMay 12, 2005
  45. Jon SeymourMay 12, 2005
  46. Jon SeymourMay 12, 2005
  47. Jon SeymourMay 12, 2005
  48. Jan HarkesMay 12, 2005
  49. Jon SeymourMay 12, 2005
  50. Jon SeymourMay 12, 2005
  51. Junio C HamanoMay 12, 2005
  52. SeanMay 12, 2005
  53. Junio C HamanoMay 12, 2005
  54. SeanMay 12, 2005
  55. Thomas GleixnerMay 12, 2005
  56. SeanMay 12, 2005
  57. Thomas GleixnerMay 12, 2005
  58. SeanMay 12, 2005
  59. Junio C HamanoMay 12, 2005
  60. Thomas GleixnerMay 12, 2005
  61. SeanMay 12, 2005
  62. Dmitry TorokhovMay 12, 2005
  63. Thomas GleixnerMay 12, 2005
  64. H. Peter AnvinMay 12, 2005
  65. H. Peter AnvinMay 12, 2005
  66. Joel BeckerMay 12, 2005
  67. Thomas GleixnerMay 12, 2005
  68. Jon SeymourMay 13, 2005
  69. Thomas GleixnerMay 13, 2005
  70. Petr BaudisMay 13, 2005
  71. H. Peter AnvinMay 13, 2005
  72. Petr BaudisMay 13, 2005
  73. Jon SeymourMay 13, 2005
  74. Jon SeymourMay 14, 2005

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.