claytonaalves

So you split a big work into stacked branches (brach B3 depending on B2 that depends on B1). What happens when the changes on B1 are not accepted? You have to rewrite the entire branch stack.

I'm impressed with how we moved from "AI is dangerous", "Skynet", "don't give AI internet access or we are doomed", "don't let AI escape" to "Hey AI, here is internet, do whatever you want".

I work with Makefiles on Delphi/FreePascal projects.

Why not just use a canvas or a SVG ?

> Does the author actually use Windows XP?

I've switched to XP (from Windows 7, on a VM) and the performance is astounding even on limited hardware settings. No bloatware, just good old Win32 x86.

This repo is private. Can u make it public ?

Well here is the workflow we use here at our company:

Branch feature from master/main.

Keep feature branch in sync with master/main (merging from master/main everyday). This minimizes conflicts when we finally get to merge feature branch to master.

Any refactor made in feature branch may be cherrypicked to master any time. This reduces differences between feature branch and master/main, resulting in less code to review.

Ctrl+l clears screen. This is very useful even if you are inside a REPL like python, ruby, mysql, etc...

"Using ZFS as a replacement of Git for is probably not a good idea..."

Of course not.

Every single day of my life.