From: "Christian MICHON" <christian.michon@gmail.com>
To: git@vger.kernel.org
Subject: Re: cygwin, 44k files: how to commit only index?
Date: Thu, 7 Dec 2006 22:26:30 +0100 [thread overview]
Message-ID: <46d6db660612071326m4817165l992e8d6e7bd673c5@mail.gmail.com> (raw)
In-Reply-To: <20061207193555.GD12143@spearce.org>
On 12/7/06, Shawn Pearce <spearce@spearce.org> wrote:
> Shawn Pearce <spearce@spearce.org> wrote:
> > Its Cygwin/NTFS. lstat() is slow. readdir() is slow. I have the
> > same problem on my Cygwin systems.
>
> Just to be clear, I'm not trying to blame Cygwin here.
>
> Windows' dir command is slow. Windows Explorer is slow while
> browsing directories. Eclipse chugs hard while doing any directory
> scans (it normally runs very fast if its not rescanning the entire
> directory structure). The drive is just plain slow.
> (...)
before buying any new hardware, you could easily imagine the
following scenario (I'm also "stuck" with windows, so it's an idea
I've been toying around for a week or so).
There're virtualizers around, on which networking capabilities can
be activated. And we could easily create a vm with linux+git
inside, using ext2/ext3/ext4 fs virtual disks (you'd benefit from
windows cache actually...)
example: YTech_Subversion_Appliance_v1.1 (ubuntu + subversion).
I've no prototype yet, but I've 2 scenario possible:
1) use vmplayer and a minimal uclibc initramfs with git onboard
2) use qemu+kqemu and a similar mini-distro (but right now networking
is an issue on windows hosts: I'm exploring tunneling)
The 1st scenario is "easy". And I start to prefer this idea over
even mingw porting of git (I tried and it's hard, really).
But again, maybe jgit would be a better universal solution.
--
next prev parent reply other threads:[~2006-12-07 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 14:27 cygwin, 44k files: how to commit only index? Alex Riesen
2006-12-07 19:16 ` Junio C Hamano
2006-12-07 19:26 ` Shawn Pearce
2006-12-07 19:35 ` Shawn Pearce
2006-12-07 21:26 ` Christian MICHON [this message]
2006-12-09 8:27 ` Torgil Svensson
2006-12-07 19:57 ` Junio C Hamano
2006-12-07 20:29 ` Shawn Pearce
2006-12-07 21:53 ` Junio C Hamano
2006-12-07 22:15 ` Alex Riesen
2006-12-07 22:29 ` Junio C Hamano
2006-12-08 5:27 ` Alex Riesen
2006-12-08 6:54 ` Junio C Hamano
2006-12-08 7:27 ` Alex Riesen
2006-12-08 7:36 ` Junio C Hamano
2006-12-08 7:48 ` Alex Riesen
2006-12-08 8:43 ` Alex Riesen
2006-12-08 14:16 ` Alex Riesen
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=46d6db660612071326m4817165l992e8d6e7bd673c5@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=git@vger.kernel.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).