Timeline for How hash is calculated for commit vs tree vs blobs?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2018 at 14:42 | history | edited | Jörg W Mittag | CC BY-SA 4.0 |
added 189 characters in body
|
| Jul 24, 2017 at 16:27 | vote | accept | appu | ||
| Jul 3, 2017 at 1:13 | comment | added | ElpieKay | A tag doesn't need to point to a commit. Any Git object can be tagged. | |
| Jul 2, 2017 at 16:58 | history | edited | Jörg W Mittag | CC BY-SA 3.0 |
added 44 characters in body
|
| Jul 2, 2017 at 16:27 | comment | added | torek |
One minor correction: notes are stored as commits, containing trees containing files. refs/notes/commits points to the tip-most of a chain of such commits. The tree associated with this tip-most commit has one file per commit-that-has-a-note: if there is a note for commit badf00..., for instance, there is a file named ba/df00... or ba/df/00... or similar in the "tip note". That file (a blob) contains the notes for commit badf00.... The degree of fan-out here depends on the number of noted commits.
|
|
| Jul 2, 2017 at 15:33 | history | edited | Jörg W Mittag | CC BY-SA 3.0 |
added 120 characters in body
|
| Jul 2, 2017 at 15:16 | history | edited | Jörg W Mittag | CC BY-SA 3.0 |
added 1952 characters in body
|
| Jul 2, 2017 at 15:02 | history | answered | Jörg W Mittag | CC BY-SA 3.0 |