Doesn't Git make this rather easy, though? e.g. you can find all deleted files with: git log --diff-filter=D --summary and find a specific file with (showing glob patterns): git log --all --full-history -- **/thefile.* and then show it: git show <SHA> -- <path-to-file> or restore it: git checkout <SHA>^ -- <path-to-file> https://stackoverflow.com/questions/7203515/git-how-to-search-for-a-deleted-file-in-the-project-commit-history On Wednesday, November 29, 2017 12:26:01 PM CST, Serhiy Storchaka wrote: > After removing files from the repository they disappear from > the source tree, and it is even hard to notice this if you don't > use it regularly. It is hard to track the history of the removed > file even if you know it exact path. If you know it only > approximate this is harder. > > I think that any file removals from the repository should pass > some PEP-like process. Declaring the intention with the > rationale, taking a feedback, discussing, and finally > documenting the removal. Perhaps it is worth to track all > removals in a special file, so if later you will find that the > removed file can be useful you could restore it instead of > recreating its functionality from zero in the case if you even > don't know that similar file existed. > -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4