From: Chris Malton <chrism@cjsoftuk.dyndns.org>
To: linux-fsdevel@vger.kernel.org
Subject: NCPFS and extended characters (Charcode >=128)
Date: Wed, 23 May 2007 18:06:10 +0100 [thread overview]
Message-ID: <46547482.8030403@cjsoftuk.dyndns.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 247 bytes --]
Hello,
NCPFS has an undesirable bug (IMHO) where any character above charcode
127 will prevent the directory listing from showing.
Could somebody either work out how to fix it, or better still, fix it
and commit?
Thank you in advance,
Chris
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2146 bytes --]
reply other threads:[~2007-05-23 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46547482.8030403@cjsoftuk.dyndns.org \
--to=chrism@cjsoftuk.dyndns.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).