William Lieurance
Julia Evansnow that Git 2.53 is out, the Git data model @omarieclaire and I wrote is on the official Git website! https://git-scm.com/docs/gitdatamodel
Frederik Braun οΏ½@b0rk @omarieclaire congrats!
nathan@omarieclaire @b0rk congratulations π
Peter Krefting@b0rk @omarieclaire Well done and well written! Thank you
Miguel de Icaza α―
π@b0rk @omarieclaire brilliant!
Ricardo Signes 
@b0rk @omarieclaire Congratulations, that's going to help a lot of people!
pseudoramble@b0rk @omarieclaire didn't get to finish it yet but this was a great read so far. Really easy to understand.
Olly Maunder@b0rk @omarieclaire Git documentation that's actually readable!
Boris Schapira (Pro)@b0rk @omarieclaire achievement! π
lambdageek@b0rk @omarieclaire this is so good
Like is it even legal to write git docs that don't say "<treeish>" even once
@lambdageek i was surprised & very happy that there was really zero resistance to leaving out the term "treeish"
OwenT@b0rk @lambdageek is it bad that I ctrl-f'd for 'treeish' before even reading this comment
Andy Norman@b0rk @omarieclaire very informative π
Turns out I had misunderstood a key part of git. I had thought it stored diffs/deltas, but I now know it stores the entire contents of any changed file in a commit.
Quite how Iβve managed to got this many years without realising that, I donβt know π
David Culley@andynormancx @b0rk @omarieclaire There's a very good video explaining exactly that on the YouTube channel anthonywritescode.
git is not a series of patches!
Michael Boelen@b0rk @omarieclaire Awesome, well done both!
linrunner
Jason Sadler@b0rk @omarieclaire I read it recently and learned a lot. You did a phenomenal job! Congrats on the official release.
Tivadar@b0rk @omarieclaire it's easy to follow and understand!