Static and Noise
Expand Cut Tags
No cut tags
Ppl are Talking
- 1: There is also a secret truth in here about writing technical documentation, if you're looking for it
- 2: RIP Halla
- 3: More Shooting Upward: Blue Revolver
- 4: Friday night is bookpost night
- 5: An analogy occurred to me the other day.
- 6: The case of the default thread pool heuristic
- 7: Games and comics: Many Fingers, Octopus Pie, Don't Go Without Me, and Sylvie
- 8: (no subject)
- 9: You Know What I Read Last Summer
- 10: The rewrite is live!
Wet Paint
- Style: Scratch the Surface 🐾 for Cutting Corners by
Re: Yeah!!
Date: 2023-10-08 10:39 pm (UTC)Let's say I was lucky that git has the same logic as I.
For me, doing something in git is (relatively) easy, as long as you know what is your current state and what final state you want to get.
I still have problems with some behaviours that are illogical to me, like submodules.
Back to mercurial.
At work, I had to migrate from using git to hg around 2012–2013.
hg was so much confusing to me.
It was always in the way of how I used version control and I had to add a plugin or something to regain some control on my local repo, to edit commits and local history as I see fit.
I still don't understand what is gained to hardlink a commit to a branch.
Why can a branch have more than one tip?
It was very enabling for my collegue that never did a merge an just push his work as a new tip.
You can't be that lazy on git. Or you can try and others will easily see that you "forget" to merge your working branch (or push -f 🤬).
Let's just say I went happily back to git after that and let time not using hg erase what I had to learn of it.