20 years ago today, Linus made the first commit on the Git project. Here is my birthday present post, looking back.
Happy birthday git, and thanks for all the fish.
blog.gitbutler.com/20-years-of-...
This is so strange, for some reason I thought rebase preserved them. `git replay` does, which is probably why GitHub works, so it can do these in memory. I believe libgit2 does as well, so maybe they're still using that. @gitlab.com and @gitea.com don't, so they're prob shelling out to `git rebase`
Everyone rallied around moving away from “master” but we’re still collectively ok with gimp?
He’s right, your rebase also strips extra headers. Do you know where the whitelist of headers is hard coded?
We actually have a third structure, which is virtual branches - you can work on multiple branches (or stacks of branches) at the same time in one working directory. In case multiple stacks or branches have no interdependencies.
I like the two levels.
Per-commit review within a branch means they are all merged together. Stacking branches means the bottom should be merged first, but stacks above it depend on those but don’t need to be merged at the same time.
Its a useful mental difference when working on them.
Really? That seems like an unlikely reason. The signature just verifies the commit data minus the signature, it shouldn't matter what is in there for a verification. Can you point me at a use case?
In fact, if this were true, Gitea would break with any new future official git headers.
Merci
Currently no, but it's on our short list.
Not the entire history, just the commits you are trying to review.
For the last few months, @gitbutler.com has been working on a new code review tool and using it in place of PR review.
It's commit-based, treating your branch like a series of patches and it's completely changed my workflow.
Check it out!
blog.gitbutler.com/gitbutlers-n...
my god, the russian bear octocat. probably my favorite one.
If you haven't been watching, we are now on our 11th(!) episode of Bits and Booze. This latest one is us showing off libgit2 by building a simple git client in Tauri while drinking non-alcoholic wine.
www.youtube.com/watch?v=WKWf...
This is awesome.
This week in "Scott writing up dark corners of Git", it's the story of Git's new bundle-uri and issues that I found that resulted in yet another patch to Git.
blog.gitbutler.com/going-down-t...
Time for streaming some Rust/Typescript goodness with Caleb!
www.twitch.tv/gitbutler
I think they come up a few days later or something.
Once again, @gitbutler.com's Caleb is live streaming working on our upcoming review stuff. This time at a new, shorter URL that we forgot we had squatted.
www.twitch.tv/gitbutler
Scott Chacon is back in Bits & Booze Ep. 9 for Git Interview Part 2: Hard. Can he still handle the heat? Watch the fun unfold! 🍷💻
youtu.be/FbW9wlve8sI?...
Dont worry, my next post is about bundle-uri, which I think is more Derrick.
In fact, I thought I _just_ saw in the GerritForge summit video that branch based review was _maybe_ on the horizon
I’m curious. You say “series” but my last run in with Gerrit was that it was very single commit based. Even looking at the docs now, it still appears single patch based. Can you do a series of commits as a change basis now?
Another week, another super fun Git nerd article. Today I posted about doing interdiff review with the git range-diff command.
blog.gitbutler.com/interdiff-re...
Fun new blog post today about some git config values that should probably be the defaults.
blog.gitbutler.com/how-git-core...
This is how shit gets done.
Why is Git Autocorrect too fast for Formula One drivers to react to?
I dug a bit into DHH's surprise experience of noticing Git wait for only 100ms to autocorrect a command. The answer involves "deciseconds" and Levenshtein distances.
blog.gitbutler.com/why-is-git-a...
Finally, GitHub has attestations. What are those you ask?
"Attestations bind some subject (a named artifact along with its digest) to a SLSA build provenance predicate using the in-toto format."
Finally.
Can we all agree that a Prius+ is not an “XL”, Uber?
That seems like the innovation we needed. The TI keyboard is the best way to write code, I’ve found. 😂
I just learned that students today use the TI-84 graphing calculator in the classroom. When I was in high school 30 years ago, I was the first class that used the TI-81 and our teacher was trying to get used to it. But it's fascinating how _little_ this tech has really changed over that time.
