4 ms·

I understand the .git search path, but I almost never use `git clean` in my projects (usually just `git reset --hard` or `make clean`), so I've never been too w

by nixme 15y ago

I understand the .git search path, but I almost never use `git clean` in my projects (usually just `git reset --hard` or `make clean`), so I've never been too worried. But your solution is definitely safer -- although I think you meant GIT_WORK_TREE, not GIT_WORKDIR, right? I'm going to switch. Thanks! EDIT: Working nicely :) https://github.com/nixme/dotfiles/commit/64486fe25e6750567a01cea49f527686c56ea365 https://github.com/nixme/dotfiles/commit/64486fe25e6750567a0...

fr0sty 15y ago
> I... usually just `git reset --hard` This is still risky if your ~/.git had uncommitted changes. I'll admit to being a little paranoid but I spent enough time on the #git irc channel to learn that any advice that is potentially dangerous will _always_ be used in the dangerous fashion, often without knowledge of the risks. > although I think you meant GIT_WORK_TREE, not GIT_WORKDIR, right? Yeah, brain cramp on that one, sorry.