From: Michael Baldwin <m@orb.sh>
To: 9fans@cse.psu.edu
Subject: [9fans] long path names
Date: Sat, 1 Jun 2002 14:01:10 -0400 [thread overview]
Message-ID: <8DE3E682-7589-11D6-9E8E-000393726A14@orb.sh> (raw)
In-Reply-To: <20020601165932.L29024@cackle.proxima.alt.za>
now that long names are really supported in plan 9, when is the archive
format going to be fixed? it still uses the 16-char limit from the
ancient days, which even 3rd edition plan 9 could choke on (16 < 28).
other systems out there use one of i think 3 different hacks to extend
the name limit (ugh).
prev parent reply other threads:[~2002-06-01 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 13:46 [9fans] spaces in filenames Russ Cox
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 ` Michael Baldwin [this message]
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=8DE3E682-7589-11D6-9E8E-000393726A14@orb.sh \
--to=m@orb.sh \
--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).