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 20:54:52 +0100 [thread overview]
Message-ID: <514A140C.1040901@lsrfire.ath.cx> (raw)
In-Reply-To: <614e174a0b4548a1bcdc6c24c2682829@BLUPR03MB019.namprd03.prod.outlook.com>
Am 19.03.2013 22:36, schrieb Josh Rowe:
> Yes, Dedup is in fact a Server-only feature.
Is there an easier way to reproduce the issue than registering and
downloading the Windows Server 2012 evaluation version? It's not that
hard, admittedly, but still.
> The reparse point could be decoded as being a non-symlink reparse
> itemusing; in those cases, treating the file as an "ordinary"
> file would be appropriate.
>
> For example, see the following. The reparse tag value for symlinks
> isIO_REPARSE_TAG_SYMLINK (0xa000000c) and for deduped files is
> (IO_REPARSE_TAG_DEDUP) 0x80000013.
That's interesting and invalidates my initial checks with mklink,
because if I read compat/mingw.c [1] correctly then git handles symlinks
on Windows in a special way, but should treat dedup reparse points as
normal files already.
Hrm, but probably st_size is set to zero for them. Do the deduped files
appear as empty? "git ls-tree -r HEAD" would show them with a hash of
e69de29bb2d1d6434b8b29ae775ad8c2e48c5391. If true then how do we get
their real content sizes using Win32 API calls?
By the way, what does the command "git version" return for you?
Thanks,
René
[1] https://git.kernel.org/cgit/git/git.git/tree/compat/mingw.c#n427
--
--
*** 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.
next prev parent reply other threads:[~2013-03-20 19:55 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 [this message]
2013-03-20 20:43 ` Josh Rowe
2013-03-20 21:45 ` René Scharfe
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=514A140C.1040901@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).