[Clifford: forgive me for sending this post twice -- on my first attempt I hit "Reply" instead of "Reply All", and it went only to you.]
On Fri, Apr 18, 2008 at 11:05 AM, Clifford Caoile < [EMAIL PROTECTED]> wrote: > > On Fri, Apr 18, 2008 at 11:04 PM, cjl <[EMAIL PROTECTED]> wrote: > > Also, is there any way I could slim thing down? msysGit is approx. > > 100MB when extracted. > > I don't know. > > You probably want to look at how the msysgit installer is made. > > From looking at the installer source, I see it uses "CreateHardLink" > to hard link all git internal programs, for supposed space savings. > However I can't really confirm that it works, since my NTFS-based git > install directory also shows "100MB in use". > > Best regards, > Clifford Caoile > Explorer's too dumb to know about hard links. Use "du" from msysgit, from a git bash prompt, to determine the true usage. I tested this just now: $ mkdir /c/temp/du-test $ ln big-huge-file /c/temp/du-test/instance1 $ ln big-huge-file /c/temp/du-test/instance2 Explorer in this instances believes that C:\temp\du-test takes up twice the space that it should. Use the msysgit-provided du, and you get the proper result: $ cd /c/temp/du-test $ du 287753 . (Explorer claimed that C:\temp\du-test took up 562 MB (589,316,212 bytes).)
