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

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

From
DTDmitry Torokhov <dtor_core@ameritech.net>
Date
May 12, 2005, 00:41 UTC
Message-ID
<200505111941.04104.dtor_core@ameritech.net>
In-Reply-To
<1115854733.22180.202.camel@tglx>
On Wednesday 11 May 2005 18:38, Thomas Gleixner wrote:
Show 9 quoted lines
> On Wed, 2005-05-11 at 16:14 -0700, H. Peter Anvin wrote:
> > I would like to suggest a few limiters are set on the repoid.  In 
> > particular, I'd like to suggest that a repoid is a UUID, that a file is 
> > used to track it (.git/repoid), and that if it doesn't exist, a new one 
> > is created from /dev/urandom.
> 
> Which is complety error prone due to rsync. Some of the repositories on
> kernel.org keep identical copies of .git/description already. Why should
> they preserve an unique .git/repoid ?

I think that an unique repoid should be created automatically every time you clone. It is ok for it to go away when you discard a tree, it will just identify a line (set) of changes originating from some place.

-- 
Dmitry
Previous: SeanNext: Thomas Gleixner
Message 62 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.