This is a Voight-Kampff test. In a few words, tell us what you are calling about.
"Let me tell you what I'm calling about...
9 posts • joined 23 Aug 2019
The great thing about Git if that you can edit your local history by amending and doing other surgery to commits. Interactive rebase is the greatest thing after sliced bread. Once it gets to the master repo, though, there should not be any history editing going on. This can be enforced by use of code review systems.
>What sort of monumentally screwed up thinking lead to vanilla `--force` existing?
Personal repositories. I use it all the time to push to my personal build and test machines.
Instead of pushing directly to the common repository, use a code review system. You'll never need to know about --force-with-lease and such crap.
If you can transform ducomment binaries to containing text - for example, modern document formats are just a zipped bunch of XML files, you can use Git's clean/smudge attributes to transform the files from binary format in the worktree, to text format in the repository, diffable, etc.
Git is f-ing awesome. And interactive rebase is the best thing after sliced bread.
The basic concepts of history keeping and tree building are simply brilliant.
I've used: PVCS in mid-1990s - piece of shit. Initially, it didn't even support directories. Could only commit flat snapshots. Later it started to support subdirectories.
Visual Source Safe - was usable and useful for my personal projects and small team collaboration. It had its quirks. Concept of branch as a separate directory was pretty stupid. Files shared between directories was an interesting, but unmanageable concept.
Perforce: stupid ill-conceived concept of workspaces to map the repo directories to different checkout worktree struucture. Branching was so badly conceived (seperate directory, again), that I never ever dared to create them. If I created a branch, it would be global; there was no concept of local repository clone.
Git: Not easy to learn from scratch, but once you get it, it's the best. Hack the code, then slice and dice it to commits as desired, then after debug apply some surgery to those commits, and push them to the review system.
Biting the hand that feeds IT © 1998–2019