From: Linus Torvalds <torvalds@linux-foundation.org>
To: aaron@assonance.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 3/3] read_directory(): infrastructure for pathname character set conversion
Date: Thu, 14 May 2009 15:51:46 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0905141547480.3343@localhost.localdomain> (raw)
In-Reply-To: <727e50150905141536r5f3c4c1ap615166ba71018bf3@mail.gmail.com>
On Thu, 14 May 2009, Aaron Cohen wrote:
>
> Does this possibly allow using the magic "\\?\" prefix on windows to
> avoid file name length restrictions?
That would be the intention - eventually. The point being exactly that the
'path' side can be done differently from the 'basename' part that git then
uses internally.
However, the thing is not complete. As shown from the strace, almost all
filesystem operations then end up using the 'git internal' name anyway.
It's currently literally just the filesystem traversal itself that knows
to separate the notion of 'internal pathname representation' from the
filesystem accesses.
So right now, the only thing that uses the filesystem-specific stuff is
the "opendir()" (and the lstat() in case the filesystem doesn't support
d_type in the dirent).
Kubys
next prev parent reply other threads:[~2009-05-14 22:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 20:42 [PATCH 1/3] dir.c: clean up handling of 'path' parameter in read_directory_recursive() Linus Torvalds
2009-05-14 20:46 ` [PATCH 2/3] Add 'fill_directory()' helper function for directory traversal Linus Torvalds
2009-05-14 20:54 ` [PATCH 3/3] read_directory(): infrastructure for pathname character set conversion Linus Torvalds
2009-05-14 21:23 ` Linus Torvalds
2009-05-14 22:19 ` Johannes Schindelin
2009-05-14 22:36 ` Aaron Cohen
2009-05-14 22:51 ` Linus Torvalds [this message]
2009-05-14 22:47 ` Linus Torvalds
2009-05-15 19:01 ` [PATCH 4/3] Introduce 'convert_path_to_git()' Linus Torvalds
2009-05-16 6:40 ` Junio C Hamano
2009-05-16 17:27 ` Linus Torvalds
2009-05-19 12:20 ` Jens Kilian
2009-05-19 13:31 ` John Koleszar
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=alpine.LFD.2.01.0905141547480.3343@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=aaron@assonance.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).