public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Shaddy Baddah <helium@shaddybaddah.name>
To: cygwin-talk@cygwin.com
Subject: Re: managed mounts. hindsight sadness at their departure
Date: Fri, 05 Mar 2010 05:02:00 -0000	[thread overview]
Message-ID: <4B909067.8050409@shaddybaddah.name> (raw)
In-Reply-To: <4B9089A2.5070707@redhat.com>

Hi,

On 5/03/2010 4:33 AM, Eric Blake wrote:
> Request case sensitivity from windows, and you have that feature back.

How embarrassing. I recalled fleetingly seeing something on case
sensitivity in the 1.7 user manual, and checked back. But only the
CYGWIN variable section. Seeing that it was restricted to globbing
behaviour, I missed 
http://www.cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive

>> Not that I'd assert that this is reason enough to have kept the managed
>> mounts, it is just an unfortunate limitation that 1.7 now has over 1.5.
>
> No, it is not a limitation, provided you follow the instructions.
>
> $ touch a A
> $ ls ?
> A  a

Many thanks for pointing it out. I was completely unaware that Windows
was capable of case sensitive file naming. I must admit that my
entrenched views of Windows capabilities in this area make me a little
bit apprehensive of possible side-effects to turning this on. In your
experience, are there any?

Of course, I will still try it anyway.

Regards,
Shaddy

  reply	other threads:[~2010-03-05  5:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05  3:59 Shaddy Baddah
2010-03-05  4:33 ` Eric Blake
2010-03-05  5:02   ` Shaddy Baddah [this message]
2010-03-05  9:36     ` Corinna Vinschen
2010-03-08 13:29       ` Shaddy Baddah

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=4B909067.8050409@shaddybaddah.name \
    --to=helium@shaddybaddah.name \
    --cc=cygwin-talk@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).