further thoughts
This commit is contained in:
parent
f7a10dc421
commit
1744bd6b48
1 changed files with 10 additions and 0 deletions
|
@ -7,3 +7,13 @@ inability to quickly grep locally present files
|
|||
run "git annex grep"
|
||||
|
||||
> i don't understand this request. just running `grep` will grep all the locally present files: sure there will be warnings, but you can use `2>/dev/null` to silence those. as for the suggested solution in comment, that greps for the filenames. please clarify the feature request here or this is [[invalid|done]]. --[[anarcat]]
|
||||
|
||||
>> The reason `git grep` exists is partly speed (git objects can
|
||||
>> sometimes be read more efficiently than traversing the fileststem),
|
||||
>> and partly the ability to grep a whole tree of source code, but
|
||||
>> avoid grepping build artifacts, etc. The former reason doesn't apply
|
||||
>> with git-annex. The latter reason applies somewhat, but it's much less
|
||||
>> common to want to grep large binary files than it is to want to grep a
|
||||
>> source tree. `git annex find` can be fed to `grep` when one wants to do
|
||||
>> that. So I don't see a compelling case to add this to git-annex.
|
||||
>> --[[Joey]]
|
||||
|
|
Loading…
Reference in a new issue