From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Josh Rowe <Joshua.Rowe@microsoft.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"msysgit@googlegroups.com" <msysgit@googlegroups.com>
Subject: Re: FW: Windows. Git, and Dedupe
Date: Wed, 20 Mar 2013 22:45:20 +0100 [thread overview]
Message-ID: <514A2DF0.2080708@lsrfire.ath.cx> (raw)
In-Reply-To: <2156b5b7b012490490c1b52637a6164a@BLUPR03MB019.namprd03.prod.outlook.com>
Am 20.03.2013 21:43, schrieb Josh Rowe:
> If you have Win8 or HyperV 2012, I can ship you a small NTFS .vhd
> with some deduped files. I'm not sure if that will be readable, but
> I would hazard a guess that it would be. It definitely will not be
> readable on Win7.
It would be nice if you could upload it to an FTP server or website and
post a public link so that the real git-on-Windows developers can get it
as well. You can also send it to me personally and I'll see if I can
mount it using Windows 8 and where I get from there. In any case,
please make sure there's no sensitive or private data in the VHD file.
How big is it after compression using (preferably) 7-Zip or ZIP?
> I'm using:
>
> PS C:\> git version git version 1.8.0.msysgit.0
That means compat/mingw.c is directly relevant to you; more about MinGW,
MSys and git at http://msysgit.github.com/ and http://mingw.org/.
> The file sizes show up as their original size with Windows tools
> (powershell, Win32, cmd, .Net, etc). git ls-tree -r HEAD does not
> show that hash code for files that are not intentionally empty.
So we can likely (hopefully) get the sizes of deduped files with the
same API calls as for regular ones. Which makes me even more puzzled
over the question of why git makes a difference between the two kinds.
René
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
prev parent reply other threads:[~2013-03-20 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 21:20 FW: Windows. Git, and Dedupe Josh Rowe
2013-03-19 21:08 ` René Scharfe
2013-03-19 21:36 ` Josh Rowe
2013-03-20 19:54 ` René Scharfe
2013-03-20 20:43 ` Josh Rowe
2013-03-20 21:45 ` René Scharfe [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=514A2DF0.2080708@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=Joshua.Rowe@microsoft.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
/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).