git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Cohen <remleduff@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	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 18:36:24 -0400	[thread overview]
Message-ID: <727e50150905141536r5f3c4c1ap615166ba71018bf3@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0905150018070.26154@pacific.mpi-cbg.de>

On Thu, May 14, 2009 at 6:19 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Thu, 14 May 2009, Linus Torvalds wrote:
>
>> The use of "//" as the filesystem path component separator may be odd,
>
> Hopefully it will not bite us on Windows: "//fileserver/x" is different
> from "/fileserver/x" there: the former tries to access the share "x" of
> samba server "fileserver", while the latter will expand to "C:\Program
> Files\Git\fileserver\x" (or wherever you installed Git).
>
> Ciao,
> Dscho

Does this possibly allow using the magic "\\?\" prefix on windows to
avoid file name length restrictions?
-- Aaron

  reply	other threads:[~2009-05-14 22:36 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 [this message]
2009-05-14 22:51         ` Linus Torvalds
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=727e50150905141536r5f3c4c1ap615166ba71018bf3@mail.gmail.com \
    --to=remleduff@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=aaron@assonance.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).