Timeline for How hash is calculated for commit vs tree vs blobs?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 24, 2017 at 16:27 | vote | accept | appu | ||
| Jul 2, 2017 at 22:05 | answer | added | Philippe | timeline score: 3 | |
| Jul 2, 2017 at 16:31 | comment | added | torek | See also github.com/chris3torek/scripts/blob/master/githash.py (computes hashes for files and trees in the same way as Git does). | |
| Jul 2, 2017 at 15:12 | comment | added | Ry-♦ | @appu: Copy and paste error, sorry. | |
| Jul 2, 2017 at 15:05 | comment | added | appu | @TimBiegeleisen It matters to me to really understand how git command actually affects the object storage. IMHO, if one doesn't know how things are formed then u really can't be at ease with it, atleast I don't. | |
| Jul 2, 2017 at 15:02 | answer | added | Jörg W Mittag | timeline score: 12 | |
| Jul 2, 2017 at 14:58 | comment | added | appu | @Ryan Trees do have trees (directories) and blobs but not parent, authors, committers, or messages. | |
| Jul 2, 2017 at 14:20 | comment | added | Tim Biegeleisen | Playing the devil's advocate, why does it matter to you how SHA-1 hashes are calculated, assuming that an algorithm is used which makes it reasonably unlikely that a collision would ever occur? | |
| Jul 2, 2017 at 14:17 | comment | added | Ry-♦ | No. Blobs don’t have trees, parent commits, authors, committers, or messages. Trees don’t have parent commits, authors, committers, or messages. | |
| Jul 2, 2017 at 14:16 | history | edited | Ry-♦ | CC BY-SA 3.0 |
Formatting
|
| Jul 2, 2017 at 14:13 | history | asked | appu | CC BY-SA 3.0 |