From: "Niklas Höglund" <nhoglund@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 13:59:17 +0000 [thread overview]
Message-ID: <1170597557.7538.12.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0702031733190.8424@woody.linux-foundation.org>
On Sat, 2007-02-03 at 17:17 -0800, Linus Torvalds wrote:
> Here's a clue:
>
> include/linux/netfilter/xt_dscp.h
> include/linux/netfilter/xt_DSCP.h
>
> are both tracked files..
Oh. It never struck me that people would use the "same" name for two
different things. I thought it was something more subtle, like I file
being renamed from one case to another. I should have looked a bit more
carefully.
On Sat, 2007-02-03 at 17:38 -0800, Linus Torvalds wrote:
> On Sat, 3 Feb 2007, Junio C Hamano wrote:
> >
> > Are there plans to "fix" the confusion by renaming them to
> > reduce chances of name clashes on such suboptimal filesystems?
>
> I don't think so. Nobody really does development on such broken
> filesystems, and I kind of have this nagging suspicion that Niklas noticed
> just because he wanted to test git, not because he really wanted to do
> Linux development under Windows ;)
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
next prev parent reply other threads:[~2007-02-04 13:59 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 [this message]
2007-02-04 14:17 ` Mark Levedahl
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=1170597557.7538.12.camel@localhost \
--to=nhoglund@gmail.com \
--cc=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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.