2 ms·
Not sure why the article left out `git ls-tree -r`: this is as good as doing ls-files at any commit (given as argument), not just at what's currently checked ou
by penguin_booze 3y ago
Not sure why the article left out `git ls-tree -r`: this is as good as doing ls-files at any commit (given as argument), not just at what's currently checked out.
- malingo 3y agogit diff-tree [1] is also super helpful. I've use it a lot to ensure the codebase after a complex rebase is in an identical state as before. [1] https://git-scm.com/docs/git-diff-tree https://git-scm.com/docs/git-diff-tree