git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Junio C Hamano" <junkio@cox.net>,
	"Git Mailing List" <git@vger.kernel.org>,
	"Niklas Höglund" <nhoglund@gmail.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: git and file name case on cygwin
Date: Sun, 4 Feb 2007 16:01:31 +0100	[thread overview]
Message-ID: <20070204150131.GA15726@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702031733190.8424@woody.linux-foundation.org>

On Sat, Feb 03, 2007 at 05:38:16PM -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 ;)

At my present work we do all development under Windows and this is what
we have used since day one. Shifting the underlying OS to Linux last
year should not and did not trigger a development environment revolution
(read: change to Linux).

But it would still be preferable to actually build the Linux kernel on
Windows so there is no need to do a remote build for part of the
system and the rest on the Windows host.
Or in other words to make the kernel build able on Windows does not imply
the desire to actually do kernel development on Windows.

	Sam

      parent reply	other threads:[~2007-02-04 15:34 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
2007-02-04 14:27         ` Jakub Narebski
2007-02-04 15:01       ` Sam Ravnborg [this message]

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=20070204150131.GA15726@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --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 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).