From: Yura Pakhuchiy <pakhuchiy@iptel.by>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Print inode number if name can not be represented in the local charset
Date: Thu, 21 Jul 2005 16:27:34 +0300 [thread overview]
Message-ID: <1121952454.2027.25.camel@chaos.void> (raw)
In-Reply-To: <1121952107.17221.84.camel@imp.csi.cam.ac.uk>
On Thu, 2005-07-21 at 14:21 +0100, Anton Altaparmakov wrote:
> On Fri, 2005-07-01 at 05:03 +0300, Yura Pakhuchiy wrote:
> > This patch changes message type from ntfs_error to ntfs_debug in the
> > unistr.c when unicode filename contains characters that can not be
> > converted into the local charset, because it's not useful for user and
> > actually it's not a error. Instead of this print warning in dir.c, this
> > warning includes inode number for further investigation (e.g. with
> > ntfsinfo).
>
> I applied something simillar to your patch to my private tree so it will
> be in the next ntfs release. Thanks for the patch.
Great! Thanks.
--
Best regards,
Yura
prev parent reply other threads:[~2005-07-21 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 2:03 Print inode number if name can not be represented in the local charset Yura Pakhuchiy
2005-07-21 13:21 ` Anton Altaparmakov
2005-07-21 13:27 ` Yura Pakhuchiy [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=1121952454.2027.25.camel@chaos.void \
--to=pakhuchiy@iptel.by \
--cc=aia21@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pakhuchiy@gmail.com \
/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).