From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in filenames
Date: Sat, 1 Jun 2002 09:46:10 -0400 [thread overview]
Message-ID: <68ae0f680a3752663a0ced5488e6784d@plan9.bell-labs.com> (raw)
looks like you pulled in a big one, geoff.
where do you get such great lures?
next reply other threads:[~2002-06-01 13:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 13:46 Russ Cox [this message]
2002-06-01 14:34 ` [9fans] lures Michael Baldwin
2002-06-01 14:59 ` Lucio De Re
2002-06-01 17:54 ` [9fans] spaces, separators, and utf-8 Michael Baldwin
2002-06-01 18:21 ` Scott Schwartz
2002-06-01 22:00 ` Dan Cross
2002-06-01 18:01 ` [9fans] long path names Michael Baldwin
-- strict thread matches above, loose matches on Subject: below --
2011-04-26 18:08 [9fans] spaces in filenames smiley
2011-04-26 18:42 ` Rob Pike
2011-04-26 18:44 ` erik quanstrom
2011-04-26 18:52 ` dexen deVries
2011-04-26 19:31 ` Rob Pike
2011-04-26 19:35 ` Paul Lalonde
2011-04-27 13:10 ` Digby Tarvin
2011-04-27 13:16 ` erik quanstrom
2011-04-27 13:21 ` Steve Simon
2011-04-28 9:58 ` Peter A. Cejchan
2011-04-26 18:43 ` erik quanstrom
2011-04-27 2:30 ` smiley
2011-04-27 2:39 ` erik quanstrom
2002-06-03 12:42 presotto
2002-06-01 22:17 Russ Cox
2002-06-01 22:25 ` William Josephson
2002-06-03 10:06 ` Axel Belinfante
2002-06-01 22:16 Russ Cox
2002-06-01 14:55 Richard Miller
2002-06-01 14:16 Russ Cox
2002-06-01 14:15 Russ Cox
2002-06-01 14:10 Russ Cox
2002-06-01 14:38 ` William Josephson
2002-06-01 14:01 Russ Cox
2002-06-01 13:55 Richard Miller
2002-06-01 14:05 ` William Josephson
2002-06-01 13:15 ` Sam
2002-06-01 5:02 Geoff Collyer
2002-06-01 13:41 ` Michael Baldwin
2002-06-01 3:35 Michael Baldwin
2002-06-01 16:54 ` Digby Tarvin
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=68ae0f680a3752663a0ced5488e6784d@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).