3 ms·
Well, admittedly my current situation lends itself well to 'worktree' where normally a stash is probably just fine. At the moment I'm doing a big rework (porti
by smazga 10y ago
Well, admittedly my current situation lends itself well to 'worktree' where normally a stash is probably just fine.
At the moment I'm doing a big rework (porting our software from a 10 year-old OS to CentOS 7), so I have many, many modified files (all tiny mods to fix new compiler warnings from new toolchains) and untracked and obsoleted files.
Basically, it's too much for me to keep track of if I change anything, so it's a case of "whatever you do, don't touch" that pushes me toward the worktree solution.
I've been pulled in to work on customer escalations on released code (one instance from 2 releases ago), so it's just easier for me to create a whole new worktree.
I imagine that once I'm back into a normal dev cycle that I'll be back to stashing.