News for hackers. Stuff that matters.
Re:The Git history command deserves more attention by bonzini on Tuesday July 14, 2026 @01:35AM (#48902669)
So you're "spending effort in perfectly curating git history" and agreeing with your parent comment.
Re:The Git history command deserves more attention by ozim on Tuesday July 14, 2026 @02:22AM (#48902932)
Just squash everything before merging and call it a day

That is also a line from top comment. Everyone read „perfectly curating git history” and went rage commenting instead of reading and understanding what OP wrote.

Re:The Git history command deserves more attention by bonzini on Tuesday July 14, 2026 @03:06AM (#48903191)
Nope. Perfectly curating history is indeed the opposite of squashing—you squash because you couldn't be bothered to curate your commits. Squashing is a workaround not an alternative solution.
Re:The Git history command deserves more attention by ozim on Tuesday July 14, 2026 @08:52AM (#48906077)
You just contradicted your previous comment that was pointing out that fcraaldo is „spending effort in perfectly curating history” … or your comment was a joke with no indication it is a joke.
Re:The Git history command deserves more attention by bonzini on Tuesday July 14, 2026 @12:01PM (#48908881)
I interpreted "I squashed them" as "I used git rebase -i to squash the oopses and fixes". If that's not what the user does, and rather squashes the PRs, then indeed I would be disagreeing with him.
Re:The Git history command deserves more attention by skydhash on Tuesday July 14, 2026 @09:59AM (#48907010)
Yep, the curated history is the main branch, which the PR targets. The commit log in the Pr reflects the workflow of the author, which I have no interest in. As the reviewer, I’m only interested in the content (the description and the composite diff of the whole PR). I don’t review commit by commit.