9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <brucee@chunder.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] acme: some thoughts about design
Date: Mon, 31 May 2004 20:17:20 +1000	[thread overview]
Message-ID: <40BB0630.4070800@chunder.com> (raw)
In-Reply-To: <89e699eaf26eec3fc1006ff398eb84ff@9srv.net>

directed, of course - that's what walk does.
but not necessarily acyclic, unless you have
a really uninteresting namespace.  that's why
cp -r is fraught with peril.

brucee

a@9srv.net wrote:
> i don't think anybody's seriously questioning the general
> utility of search capabilities. but the directed graph we
> currently have is very useful for all sorts of things. it
> is, for example, a very "natural" (but see later) layout
> for source trees and related documentation.


  reply	other threads:[~2004-05-31 10:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29 16:51 Tiit Lankots
2004-05-29 16:58 ` Tristan Seligmann
2004-05-29 17:34   ` dvd
2004-05-30  3:49     ` Joel Salomon
2004-05-29 22:48   ` boyd, rounin
2004-05-29 23:56     ` Tristan Seligmann
2004-05-29 23:54       ` boyd, rounin
2004-05-29 23:59       ` boyd, rounin
2004-05-30  0:51         ` Tristan Seligmann
2004-05-30  3:40           ` Joel Salomon
2004-05-31  9:19           ` a
2004-05-31 10:17             ` Bruce Ellis [this message]
2004-05-30 18:09         ` Bruce Ellis
2004-05-29 17:40 ` Matthias Teege
2004-05-29 22:43 ` boyd, rounin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  7:18 cej
2004-06-04 12:52 cej
2004-06-04 18:21 ` boyd, rounin
2004-06-03  7:48 cej
2004-06-03  9:10 ` boyd, rounin
2004-06-03  9:51   ` Matthias Teege
2004-06-03 10:14     ` boyd, rounin
2004-06-03 11:22       ` Matthias Teege
2004-06-03 11:34         ` boyd, rounin
2004-06-02 11:22 cej
2004-06-02 12:42 ` a
2004-06-02 12:55   ` a
2004-05-28  9:01 cej
2004-05-29  9:28 ` Matthias Teege

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=40BB0630.4070800@chunder.com \
    --to=brucee@chunder.com \
    --cc=9fans@cse.psu.edu \
    /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).