threads / discuss / 5321

Why git-ls-tree has no --stdin option?

Subject: Why git-ls-tree has no --stdin option?

## tl;dr

3 messages between Aug 18, 2006 and Aug 18, 2006.

replies: 2people: 2as markdown or json

Jakub Narebski· Aug 18, 2006, 10:40 UTC · lore

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?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Junio C Hamano· Aug 18, 2006, 17:39 UTC · re: Jakub Narebski · lore

Re: Why git-ls-tree has no --stdin option?

Jakub Narebski <jnareb@gmail.com> writes:
> 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.

> 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

Jakub Narebski· Aug 18, 2006, 17:44 UTC · re: Junio C Hamano · lore

Re: Why git-ls-tree has no --stdin option?

Junio C Hamano wrote:
Show 10 quoted 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. 
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

← back to recent threads