3 ms·
If you run git stash with the -u option (`git stash -u`), then it will also stash untracked files. IMO leaving uncommitted/unignored files around is asking for
by nicoburns 6y ago
If you run git stash with the -u option (`git stash -u`), then it will also stash untracked files. IMO leaving uncommitted/unignored files around is asking for trouble. It's far too easy to accidentally delete or commit them. Why not have a prefix that you use for these files, and use a wildcard gitignore?
- Rusky 6y agoI'm perfectly aware of `git stash -u` ("by default") as well as `git add -N`, etc, but as I also very intentionally pointed out, that has its own downsides. That is, my own personal workflow poses essentially zero risk of deleting or committing those files, so "quit using the file system the way I've always used it" is no less of a stumbling block for me than "maintain `mod` declarations" is for you. We simply haven't found an approach that doesn't step on someone's toes, so the one that Rust was already using from the 2015 edition stuck.
- nicoburns 6y agoHmm... would you object to `use` automatically linking in modules without a `mod` declaration? It seems that that would work in the situations with regard to stashing (a git stash that stashed `mod` statements would also stash `use` statements).