Rendered at 22:17:20 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
chmaynard 2 days ago [-]
It would be useful to mention that
$ git reset ~HEAD
doesn't specify a reset mode, so the default mode --mixed is used. I prefer to use
$ git reset --soft ~HEAD
which leaves both the working tree and index unchanged.
Remnant44 1 days ago [-]
I'm one of the weirdos that still holds on to mercurial as I genuinely prefer it's methods and workflow to git most of the time.
How the author describes handling work trees is exactly how they work in hg, and I find it enormously convenient vs the way that git by default really wants you to branch with work trees.
evanjrowley 2 days ago [-]
How I use them: My big expensive mechanical keyboard collection is mostly using QMK firmware. For whichever keyboards I'm currently using, I have a git worktree per-keyboard.
nicwolff 1 days ago [-]
Note that, since the 2.55.0 release this June, git offers "instant fixup" as "git history fixup <SHA>"
How the author describes handling work trees is exactly how they work in hg, and I find it enormously convenient vs the way that git by default really wants you to branch with work trees.
https://git-scm.com/docs/git-history
Then I found the article links to jj homepage