8/31/2023 0 Comments Grep github![]() ![]() If you notice any problems with it, just drop me a note (here, or via IRC). It’s a bit picky about unresolved conflicts though. known to git (present in the HEAD commit or git added). … at slight filesystem cost ( find does access the filesystem), but on the other hand, almost all (not search depth-specific stuff) of find works, and you only get to operate on files “in the index”, i.e. It can also pass the file list to regular find(1) if it’s not too long (it must be passed on the command line), which allows for things like… git find -mtime -100 below the current working directory) path, some of them case-insensitively ( -iname and friends), and two global options, one to toggle regexp between POSIX Basic (default) and POSIX Extended, the other toggles symlinks (default on) this finds only files (and symlinks), not directories or submodules (“gitlinks”) by design. It has a couple more options, most of which handle with filtering the name or full (partial, i.e. ![]() Git find '*middleware*' # which is short forĬombining is also possible (and almost as flexible as regular find, you just have to write the -a explicitly): git find \( -name \*.java -o -name \*.js \) -a ! -ipath \*/test/\* ![]() It can be used in several modes, the easiest of which is indeed: git find \*middleware\* # or I have the same problem regularily, and I just went and hacked git find – if you don’t use the Debian package you can just copy the git-find script to /usr/lib/git-core/ (or comparable) and enjoy it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |