News for hackers. Stuff that matters.
Re:Why large companies and fast-moving startups are banning ... by tomasreimers on Friday December 29, 2023 @04:43PM (#38810559)
At some point, we decided that proposed changes (patches) should live in source control before they were approved and brought into history. In my view, this is where the problem lives.

I don't care about having an immutable record of the history of patches the same way I don't care about having an immutable record of your keystrokes as you produced the change. That's an implementation detail.

However, once something is merged into trunk, I want to know what was merged, when it was merged, who merged it, and any people who approved it.

Re:Why large companies and fast-moving startups are banning ... by jacobegold on Friday December 29, 2023 @04:55PM (#38810693)
The funny thing is — this is actually different from how OSS (the initial model that Git was built for) worked. Patches are just applied as a single linear commit to the trunk branch.

Committing the history of individual work to the source of truth remote was definitely not the intent of merges.