From: David Kastrup <dak@gnu.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Reece Dunn <msclrhd@googlemail.com>, git@vger.kernel.org
Subject: Re: [RFC] File system difference handling in git
Date: Tue, 22 Jan 2008 21:21:03 +0100 [thread overview]
Message-ID: <85ve5l393k.fsf@lola.goethe.zz> (raw)
In-Reply-To: <alpine.LFD.1.00.0801220829080.2957@woody.linux-foundation.org> (Linus Torvalds's message of "Tue, 22 Jan 2008 08:56:28 -0800 (PST)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Tue, 22 Jan 2008, Reece Dunn wrote:
>>
>> 1. File name representation
>>
>> For Linux file systems (correct me if I am wrong here), they all store
>> the file name as-is. The question here is what happens on
>> Windows-based file systems (e.g. NTFS) that are being read on Linux?
>
> Generally, Linux tries to follow the conventions of the filesystem, so
> it's generally case-preserving and case-sensitive (but not normalizing in
> any way - the case sensitivity is literally a upcase lookup table, so you
> do "upcase(c1) == upcase(c2)" for each UCS-2 character, no combining or
> decomposition).
s/sensitiv/insensitiv/g
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2008-01-22 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 9:21 [RFC] File system difference handling in git Reece Dunn
2008-01-22 10:24 ` Junio C Hamano
2008-01-22 10:52 ` Reece Dunn
2008-01-22 17:44 ` Steffen Prohaska
2008-01-22 20:54 ` Jonathan del Strother
2008-01-22 16:56 ` Linus Torvalds
2008-01-22 20:21 ` David Kastrup [this message]
2008-01-22 21:32 ` Linus Torvalds
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=85ve5l393k.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.com \
--cc=torvalds@linux-foundation.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