All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Levedahl <mdl123@verizon.net>
To: "Niklas Höglund" <nhoglund@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Junio C Hamano <junkio@cox.net>,
	Git Mailing List <git@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: git and file name case on cygwin
Date: Sun, 04 Feb 2007 09:17:34 -0500	[thread overview]
Message-ID: <45C5EAFE.6030900@verizon.net> (raw)
In-Reply-To: <1170597557.7538.12.camel@localhost>

Niklas Höglund wrote:
> It's true that I don't intend to do any Linux development on a Windows
> system. I'd use a Linux system or a Linux VM for that. I do on occasion
> have a look through the Linux source code when I'm struggling with some
> badly documented hardware, but I could use a tarball for that. (I guess
> the netfilter code would still get mangled, but I can live with that.)
>
> Niklas
>   
Note that cygwin provides mananged mounts (mount -omanaged) that handles 
files whose names differ only in case. The names are of course mangled 
when exploring via native windows tools but not cygwin tools. e.g.,

t>touch file1 File1
t>ls
File1  file1
t>cmd /c dir /b
%46ile1
file1

Mark

  reply	other threads:[~2007-02-04 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03 22:00 git and file name case on cygwin Niklas Höglund
2007-02-04  1:17 ` Linus Torvalds
2007-02-04  1:25   ` Junio C Hamano
2007-02-04  1:38     ` Linus Torvalds
2007-02-04  1:44       ` Junio C Hamano
2007-02-04 13:59       ` Niklas Höglund
2007-02-04 14:17         ` Mark Levedahl [this message]
2007-02-04 14:27         ` Jakub Narebski
2007-02-04 15:01       ` Sam Ravnborg

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=45C5EAFE.6030900@verizon.net \
    --to=mdl123@verizon.net \
    --cc=davem@davemloft.net \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=nhoglund@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.