Hello, It's me again Skybuck Flying and I am reporting back on my linux kernel checkout experiments on Microsoft Windows 7:
I tried two methods, "normal clone" and "shallow clone". During the normal clone I noticed how incredibly slow it was because of "resolving deltas" so I searched with google and came across this "shallow clone" trick which uses a depth parameter on the git clone command so I decided to try it at the same time as the normal clone and low and behold, the shallow clone was 10 times faster ! (I also inspected resource consumption and it's kinda weird, it's not really a max cpu bottleneck, neither a ram limitation or harddisk speed/latency/seek problem, most likely it's caused by xor-ing or computing sha1 hashes or maybe changes on top of changes on top of changes re-building objects, maybe the linux repository does not use snapshots or something where the files are stored in full after each year or something ? Don't know, there seems to be some confusion about this on stack overflow, how this technically exactly works, anyway) However the shallow clone does show some more potential problems, this time with case-sensitivity of filenames, see below for the results: Method 1 (Normal clone): $ git clone https://github.com/SkybuckFlying/linux.git (Still in progress) Method 2 (Shallow clone): $ git clone --depth 1 https://github.com/SkybuckFlying/linux.git Results of Method 2 (Shallow clone): new@new-PC MINGW64 /e/SourceCode $ cd LinuxKernelShallowClone new@new-PC MINGW64 /e/SourceCode/LinuxKernelShallowClone $ git clone --depth 1 https://github.com/SkybuckFlying/linux.git Cloning into 'linux'... remote: Enumerating objects: 79577, done. remote: Counting objects: 100% (79577/79577), done. remote: Compressing objects: 100% (73582/73582), done. remote: Total 79577 (delta 7208), reused 32402 (delta 5184), pack-reused 0 Receiving objects: 100% (79577/79577), 213.77 MiB | 8.08 MiB/s, done. Resolving deltas: 100% (7208/7208), done. Updating files: 100% (75027/75027), done. warning: the following paths have collided (e.g. case-sensitive paths on a case-insensitive filesystem) and only one from the same colliding group is in the working tree: 'include/uapi/linux/netfilter/xt_CONNMARK.h' 'include/uapi/linux/netfilter/xt_connmark.h' 'include/uapi/linux/netfilter/xt_DSCP.h' 'include/uapi/linux/netfilter/xt_dscp.h' 'include/uapi/linux/netfilter/xt_MARK.h' 'include/uapi/linux/netfilter/xt_mark.h' 'include/uapi/linux/netfilter/xt_RATEEST.h' 'include/uapi/linux/netfilter/xt_rateest.h' 'include/uapi/linux/netfilter/xt_TCPMSS.h' 'include/uapi/linux/netfilter/xt_tcpmss.h' 'include/uapi/linux/netfilter_ipv4/ipt_ECN.h' 'include/uapi/linux/netfilter_ipv4/ipt_ecn.h' 'include/uapi/linux/netfilter_ipv4/ipt_TTL.h' 'include/uapi/linux/netfilter_ipv4/ipt_ttl.h' 'include/uapi/linux/netfilter_ipv6/ip6t_HL.h' 'include/uapi/linux/netfilter_ipv6/ip6t_hl.h' 'net/netfilter/xt_DSCP.c' 'net/netfilter/xt_dscp.c' 'net/netfilter/xt_HL.c' 'net/netfilter/xt_hl.c' 'net/netfilter/xt_RATEEST.c' 'net/netfilter/xt_rateest.c' 'net/netfilter/xt_TCPMSS.c' 'net/netfilter/xt_tcpmss.c' 'tools/memory-model/litmus-tests/Z6.0+pooncelock+poonceLock+pombonce.litmus' 'tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+pombonce.litmus' It seems there might still be some issues after the checkout. Apperently from the looks of it the source code is developed on a file system which allows files to exist with the same alphabet letters but differentiates between capitals and small letters, which is kinda weird to be frank. And now git seems to be reporting that only one of them was checkout. So I suspect that one of each is missing and this may lead to compile/build problems on NTFS file systems ?! Well at least now I can get an impression of what this linux kernel development is all about ! LOL =D wiee =D Bye for now, Skybuck Flying. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/36a1debd-3fe6-4044-a6fe-5b515585563fn%40googlegroups.com.
