tree 507c38e3575df77ad5bfbbd789b97bff60397f34 $ git ls-tree -l v1.0.0pre1:lib/rainbows # shows similar output on the CLI size name 1068 actor_spawn.rb 3762 app_pool.rb 1405 base.rb 183 client.rb 1795 configurator.rb 938 const.rb 2938 dev_fd_response.rb 1367 error.rb 3180 ev_core.rb 7237 event_machine.rb d - event_machine/ 952 fiber.rb d - fiber/ 1335 fiber_pool.rb 899 fiber_spawn.rb 716 http_response.rb 2783 http_server.rb 2252 max_body.rb 2114 never_block.rb d - never_block/ 2014 process_client.rb 679 queue_pool.rb 573 read_timeout.rb 1745 response.rb d - response/ 1416 rev.rb d - rev/ 1099 rev_fiber_spawn.rb 2282 rev_thread_pool.rb 1225 rev_thread_spawn.rb 6024 revactor.rb d - revactor/ 2681 sendfile.rb 1044 server_token.rb 524 stream_file.rb 746 tee_input.rb 2531 thread_pool.rb 2178 thread_spawn.rb 3080 thread_timeout.rb 2871 writer_thread_pool.rb 3320 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