From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Dmitry Potapov" <dpotapov@gmail.com>,
git@vger.kernel.org, "Johannes Sixt" <johannes.sixt@telecom.at>,
"Junio C Hamano" <gitster@pobox.com>,
"Steffen Prohaska" <prohaska@zib.de>
Subject: Re: [PATCH] add GIT_FAST_STAT mode for Cygwin
Date: Wed, 24 Sep 2008 17:32:06 +0200 [thread overview]
Message-ID: <81b0412b0809240832g52a2f83cx69125895cc7f88b2@mail.gmail.com> (raw)
In-Reply-To: <20080924151653.GQ3669@spearce.org>
2008/9/24 Shawn O. Pearce <spearce@spearce.org>:
> Alex Riesen <raa.lkml@gmail.com> wrote:
>> 2008/9/24 Shawn O. Pearce <spearce@spearce.org>:
>> >
>> > However Dmitry pointed out that he has cases where this faster
>> > function doesn't work correctly, and it was path specific. Some
>> > areas of the filesystem work, others don't, on the same system.
>>
>> Huh?! What are they? What paths require cygwin's handling
>> which aren't handled already? (the absolute paths are handled).
>
> Cygwin lets you mount a filesystem at a different part of the
> filesystem.
Ewwww... Yes, you're right. Disgusting feature. Just when I
thought Cygwin cannot get any worse...
Config parameter looks like the only way to workaround that.
> Sort of like Linux's mount -t bind (IIRC).
Except that in Linux the binding is part of the filesystem namespace,
not a special knowledge of some stupid library.
next prev parent reply other threads:[~2008-09-24 15:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 14:06 [PATCH] add GIT_FAST_STAT mode for Cygwin Dmitry Potapov
2008-09-23 14:37 ` Alex Riesen
2008-09-23 16:52 ` Dmitry Potapov
2008-09-23 17:51 ` Jakub Narebski
2008-09-24 11:25 ` Alex Riesen
2008-09-24 14:03 ` Dmitry Potapov
2008-09-24 14:42 ` Alex Riesen
2008-09-24 15:02 ` Shawn O. Pearce
2008-09-24 15:09 ` Alex Riesen
2008-09-24 15:16 ` Shawn O. Pearce
2008-09-24 15:32 ` Alex Riesen [this message]
2008-09-23 15:31 ` Shawn O. Pearce
2008-09-23 17:12 ` Dmitry Potapov
2008-09-23 19:06 ` Shawn O. Pearce
2008-09-23 20:04 ` Dmitry Potapov
2008-09-23 20:17 ` Shawn O. Pearce
2008-09-23 21:28 ` Dmitry Potapov
2008-09-23 21:58 ` Shawn O. Pearce
2008-09-23 19:03 ` Johannes Sixt
2008-09-23 19:48 ` Dmitry Potapov
2008-09-23 20:41 ` Johannes Sixt
2008-09-23 21:11 ` Dmitry Potapov
2008-09-27 7:02 ` [PATCH v2] Add a "fast stat" " Marcus Griep
2008-09-27 8:35 ` Alex Riesen
2008-09-27 10:39 ` Dmitry Potapov
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=81b0412b0809240832g52a2f83cx69125895cc7f88b2@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.sixt@telecom.at \
--cc=prohaska@zib.de \
--cc=spearce@spearce.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).