From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Strange date/time on some created files
Date: Sun, 12 Feb 2006 14:53:00 +1100 [thread overview]
Message-ID: <775b8d190602111953n75c2f584i46235f6e98e908f5@mail.gmail.com> (raw)
In-Reply-To: <7d2991bd85e2b18bf1ca6b037e6f9ddc@collyer.net>
ouch, didn't think of that so what do you do? a dirread
and check the Qids that way?
brucee
On 2/12/06, geoff@collyer.net <geoff@collyer.net> wrote:
> cleanname() gets in the way of straightforward attempts to use
> `path/.', alas.
next prev parent reply other threads:[~2006-02-12 3:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 14:50 Gregory Pavelcak
2006-02-10 16:59 ` Russ Cox
2006-02-11 1:12 ` geoff
2006-02-11 15:28 ` Gregory Pavelcak
2006-02-11 15:51 ` Russ Cox
2006-02-12 2:14 ` geoff
2006-02-12 2:26 ` Russ Cox
2006-02-12 3:10 ` Bruce Ellis
2006-02-12 3:36 ` geoff
2006-02-12 3:53 ` Bruce Ellis [this message]
2006-02-12 11:06 ` Russ Cox
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=775b8d190602111953n75c2f584i46235f6e98e908f5@mail.gmail.com \
--to=bruce.ellis@gmail.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).