You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

doc.go 4.2KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. // Package commitgraph implements encoding and decoding of commit-graph files.
  2. //
  3. // Git commit graph format
  4. // =======================
  5. //
  6. // The Git commit graph stores a list of commit OIDs and some associated
  7. // metadata, including:
  8. //
  9. // - The generation number of the commit. Commits with no parents have
  10. // generation number 1; commits with parents have generation number
  11. // one more than the maximum generation number of its parents. We
  12. // reserve zero as special, and can be used to mark a generation
  13. // number invalid or as "not computed".
  14. //
  15. // - The root tree OID.
  16. //
  17. // - The commit date.
  18. //
  19. // - The parents of the commit, stored using positional references within
  20. // the graph file.
  21. //
  22. // These positional references are stored as unsigned 32-bit integers
  23. // corresponding to the array position within the list of commit OIDs. Due
  24. // to some special constants we use to track parents, we can store at most
  25. // (1 << 30) + (1 << 29) + (1 << 28) - 1 (around 1.8 billion) commits.
  26. //
  27. // == Commit graph files have the following format:
  28. //
  29. // In order to allow extensions that add extra data to the graph, we organize
  30. // the body into "chunks" and provide a binary lookup table at the beginning
  31. // of the body. The header includes certain values, such as number of chunks
  32. // and hash type.
  33. //
  34. // All 4-byte numbers are in network order.
  35. //
  36. // HEADER:
  37. //
  38. // 4-byte signature:
  39. // The signature is: {'C', 'G', 'P', 'H'}
  40. //
  41. // 1-byte version number:
  42. // Currently, the only valid version is 1.
  43. //
  44. // 1-byte Hash Version (1 = SHA-1)
  45. // We infer the hash length (H) from this value.
  46. //
  47. // 1-byte number (C) of "chunks"
  48. //
  49. // 1-byte (reserved for later use)
  50. // Current clients should ignore this value.
  51. //
  52. // CHUNK LOOKUP:
  53. //
  54. // (C + 1) * 12 bytes listing the table of contents for the chunks:
  55. // First 4 bytes describe the chunk id. Value 0 is a terminating label.
  56. // Other 8 bytes provide the byte-offset in current file for chunk to
  57. // start. (Chunks are ordered contiguously in the file, so you can infer
  58. // the length using the next chunk position if necessary.) Each chunk
  59. // ID appears at most once.
  60. //
  61. // The remaining data in the body is described one chunk at a time, and
  62. // these chunks may be given in any order. Chunks are required unless
  63. // otherwise specified.
  64. //
  65. // CHUNK DATA:
  66. //
  67. // OID Fanout (ID: {'O', 'I', 'D', 'F'}) (256 * 4 bytes)
  68. // The ith entry, F[i], stores the number of OIDs with first
  69. // byte at most i. Thus F[255] stores the total
  70. // number of commits (N).
  71. //
  72. // OID Lookup (ID: {'O', 'I', 'D', 'L'}) (N * H bytes)
  73. // The OIDs for all commits in the graph, sorted in ascending order.
  74. //
  75. // Commit Data (ID: {'C', 'D', 'A', 'T' }) (N * (H + 16) bytes)
  76. // * The first H bytes are for the OID of the root tree.
  77. // * The next 8 bytes are for the positions of the first two parents
  78. // of the ith commit. Stores value 0x7000000 if no parent in that
  79. // position. If there are more than two parents, the second value
  80. // has its most-significant bit on and the other bits store an array
  81. // position into the Extra Edge List chunk.
  82. // * The next 8 bytes store the generation number of the commit and
  83. // the commit time in seconds since EPOCH. The generation number
  84. // uses the higher 30 bits of the first 4 bytes, while the commit
  85. // time uses the 32 bits of the second 4 bytes, along with the lowest
  86. // 2 bits of the lowest byte, storing the 33rd and 34th bit of the
  87. // commit time.
  88. //
  89. // Extra Edge List (ID: {'E', 'D', 'G', 'E'}) [Optional]
  90. // This list of 4-byte values store the second through nth parents for
  91. // all octopus merges. The second parent value in the commit data stores
  92. // an array position within this list along with the most-significant bit
  93. // on. Starting at that array position, iterate through this list of commit
  94. // positions for the parents until reaching a value with the most-significant
  95. // bit on. The other bits correspond to the position of the last parent.
  96. //
  97. // TRAILER:
  98. //
  99. // H-byte HASH-checksum of all of the above.
  100. //
  101. // Source:
  102. // https://raw.githubusercontent.com/git/git/master/Documentation/technical/commit-graph-format.txt
  103. package commitgraph