tree 6708492555bff0e24cfc7bd221563577fdf38d2d $ git ls-tree -l v0.97.0:lib/rainbows # shows similar output on the CLI size name 660 acceptor.rb 1102 actor_spawn.rb 3962 app_pool.rb 3428 base.rb 354 byte_slice.rb 1862 configurator.rb 881 const.rb 2910 dev_fd_response.rb 1375 error.rb 3418 ev_core.rb 7680 event_machine.rb d - event_machine/ 304 fiber.rb d - fiber/ 1443 fiber_pool.rb 1019 fiber_spawn.rb 716 http_response.rb 2764 http_server.rb 2208 max_body.rb 2114 never_block.rb d - never_block/ 738 queue_pool.rb 1745 response.rb d - response/ 1416 rev.rb d - rev/ 1178 rev_fiber_spawn.rb 2282 rev_thread_pool.rb 1225 rev_thread_spawn.rb 6069 revactor.rb d - revactor/ 2681 sendfile.rb 1044 server_token.rb 524 stream_file.rb 746 tee_input.rb 2557 thread_pool.rb 2210 thread_spawn.rb 3080 thread_timeout.rb 2705 writer_thread_pool.rb 3154 writer_thread_spawn.rbglossary -------- Tree objects belong to commits or other tree objects. Trees may reference blobs, sub-trees, or (rarely) commits of submodules. Path names are stored in tree objects, but trees do not know their own path name. A tree's path name comes from their parent tree, or it is the root tree referenced by a commit object. Thus, this web UI relies on the `b=' URI parameter as a hint to display the path name.git clone https://yhbt.net/rainbows.git