From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on FAT32
Date: Mon, 05 Mar 2018 21:00:00 -0000 [thread overview]
Message-ID: <20180305195441.GF25306@calimero.vinschen.de> (raw)
In-Reply-To: <001501d3b4a9$ef6df5b0$ce49e110$@rogers.com>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Mar 5 12:46, Michel LaBarre wrote:
> Sorry folks but I am going to top post for the sake of clarity. The original msg is below for reference.
>
> Corinna, I ran the following and I attached the trace file:
> E:\junk>ls > Zot.txt
> E:\junk>ls
> Zot.txt
> E:\junk>strace -o d2u.trace dos2unix -n Zot.txt Zot.txt
> dos2unix: converting file Zot.txt to file Zot.txt in Unix format...
> E:\junk>ls
> ZOT.TXT d2u.trace
> [...]
Thanks. The culprit is really most likely the system. Cygwin never
observes or uses an all-uppercase name while doing its thing.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-05 19:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 9:05 Fergus Daly
2018-03-05 16:44 ` Michel LaBarre
2018-03-05 16:46 ` Corinna Vinschen
2018-03-05 17:13 ` Michel LaBarre
2018-03-05 17:16 ` Corinna Vinschen
2018-03-05 18:04 ` Michel LaBarre
2018-03-05 21:00 ` Corinna Vinschen [this message]
2018-03-06 3:20 ` Michel LaBarre
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 14:57 Fergus Daly
2018-03-06 17:58 ` Brian Inglis
2018-03-03 8:36 Fergus Daly
2018-03-03 18:14 ` Brian Inglis
2018-03-04 10:09 ` Corinna Vinschen
2018-03-04 16:14 ` Brian Inglis
2018-03-04 17:05 ` cyg Simple
2018-03-04 18:14 ` Brian Inglis
2018-03-02 9:41 Fergus Daly
2018-03-02 16:55 ` Brian Inglis
2018-03-02 17:50 ` Andrey Repin
2018-03-02 9:22 Fergus Daly
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=20180305195441.GF25306@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@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).