From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Why git-ls-tree has no --stdin option?
Date: Fri, 18 Aug 2006 19:44:54 +0200 [thread overview]
Message-ID: <ec4ual$9k8$1@sea.gmane.org> (raw)
In-Reply-To: 7v7j16aqpv.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
>> 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
prev parent reply other threads:[~2006-08-18 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 10:40 Why git-ls-tree has no --stdin option? Jakub Narebski
2006-08-18 17:39 ` Junio C Hamano
2006-08-18 17:44 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ec4ual$9k8$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).