Why git-ls-tree has no --stdin option?
Why git-ls-tree has no --stdin option to give <tree-ish> (feed it from git-ref-list for example), like git-diff-tree has? The output format could be similar: treeish, then git-ls-tree output, treeish, tree,...
Also, is there a combination of options which would display only exact matches to path limit, i.e. tree entry only if path is directory, and file (blob) entry only if path is ordinary file?
Signature · 3 lines
Jakub Narebski Warsaw, Poland ShadeHawk on #git
Quoted 3 lines · Jakub Narebski
Why git-ls-tree has no --stdin option to give <tree-ish> (feed it from git-ref-list for example), like git-diff-tree has? The output format could be similar: treeish, then git-ls-tree output, treeish, tree,...
The only reason is nobody felt need for it so far, hence nobody bothered. If you find it useful, go wild.
Quoted 3 lines
Also, is there a combination of options which would display only exact matches to path limit, i.e. tree entry only if path is directory, and file (blob) entry only if path is ordinary file?
I probably am misunderstanding the question but an empty set is the combination you want perhaps?
$ git ls-tree HEAD -- t Document sha1 sha1_name.c 100644 blob e9eb6ce882ea92523c9a871c7581457af2dc78c5 sha1_name.c 040000 tree 3fb2bfdfef59e4ed10f525ef10ad8b43b8bc459e t
Quoted 10 lines · Junio C Hamano
Quoted 3 lines
Also, is there a combination of options which would display only exact matches to path limit, i.e. tree entry only if path is directory, and file (blob) entry only if path is ordinary file?
I probably am misunderstanding the question but an empty set is the combination you want perhaps?
$ git ls-tree HEAD -- t Document sha1 sha1_name.c 100644 blob e9eb6ce882ea92523c9a871c7581457af2dc78c5 sha1_name.c 040000 tree 3fb2bfdfef59e4ed10f525ef10ad8b43b8bc459e t
Yes, thank you very much.
Signature · 3 lines
Jakub Narebski Warsaw, Poland ShadeHawk on #git