Re: [git-users] Strange effect when tar-ing a cloned repository
Hi Martin, Thanks, but my problem is not the difference between the size of the source in the git-repository and the tar-file made from the same source. Obviously tther will be differences depending on the compressing-algorithm used by tar and git. My problem is the difference between 2 tar-files. One made from the source before committing and pushing, and the second tar, made from the same source after cloneing and checking-out. I would expect them to be the same size (apart from small differences due to .gitignore etc). But an 20% increase is too much ! Regards, Peter Op maandag 19 augustus 2013 22:59:24 UTC+2 schreef Martin Møller Skarbiniks Pedersen: On 19 August 2013 21:10, peter boudewijns ing...@gmail.com javascript: wrote: Hi All, [...] When making a compressed tarball from the files from the repository (after clone/checkout) I get a very much larger tar.gz-file. Size goes up from 16M to 21M (!?) Not so strange. git is very good at compressing. One my of bare git repository is 32M but a tar.gz file of all files excluding the .git directory is 92M. /Martin -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] Strange effect when tar-ing a cloned repository
Hi Philip, Tnx for your tip. But I made 100% sure NOT to include the .git directory. And still I get a the difference between 2 tar-files. One made from the source before committing and pushing, and the second tar, made from the same source after cloneing and checking-out. I would expect them to be the same size (apart from small differences due to .gitignore etc). But an 20% increase is too much ! Regards, Peter Op maandag 19 augustus 2013 21:47:15 UTC+2 schreef Philip Oakley: - Original Message - *From:* peter boudewijns javascript: *To:* git-...@googlegroups.com javascript: *Sent:* Monday, August 19, 2013 8:10 PM *Subject:* [git-users] Strange effect when tar-ing a cloned repository Hi All, I've been trying to put my filesystem for a very small busybox-based distro into a git-repository. And with succes. The only strange thing I can not get my head around is the following : When making a compressed tarball from the files from the repository (after clone/checkout) I get a very much larger tar.gz-file. Size goes up from 16M to 21M (!?) Has anyone got a clue ? Thanks PeTer The usual reason is that you 'forgot' that the git repo itself is inside the hidden directory .git at the top level. So you have both your working tree of regular files, and then you have the hidden repo storage - so you have everything twice, and the history as well! Have a look at the 'git archive' command if you want just your your work tree, without the whole repo history. Philip -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] Strange effect when tar-ing a cloned repository
Hi tombert, No, not yet. At this moment I'm busy makeing a detailed list from all file- directory-sizes before and after git-commit/git-checkout. Thereafter I'll surely try 'git gc' ! Regards, Peter Op dinsdag 20 augustus 2013 09:28:23 UTC+2 schreef tombert: did you already try a cleanup? git gc -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] Strange effect when tar-ing a cloned repository
Hi Dale, I've been running some tests to see if I could find the origin of my size-difference. As it turned out, when examining the filesystem's size on the target with 'su', this was about 10M bigger in case of the git-cloned filesystem (I make a jffs2-file to flash the target, thereafter examine the target via a tty). The entire difference could be pinned down in just 1 directory, 'sbin'. So, I made complete listings (ls) from /sbin, both the original as the git-cloned version. And they are exactly the same !? But with su -hs the /sbin directory yields the 10M difference .. ? I do not know enough about the way Linux writes its files, and how it determines the size of the files. But it seems to me the git-cloned files contain empty space that occupies filesystem-space, but is not counted when calculating the actual filesize . Both versions function 100% on the target, so why worry ? But I still would like to know whats going on And yes, I also used git gc (--aggressive), but this yields no improvement at the client side upon cloneing/checking out. To be continued Regards, Peter My guess is that the cloned repository isn't compressed in exactly the same way as the original repository. The first step would be to find out the amount of disk space occupied by the original and the cloned repositories (using du -s) rather than depending on the size of the .tar files. If you want the repository to be small, look into git gc --aggressive. Dale Dale Worley -- Today is: 12.19.16.17.0 9 Ahaw 18 Mak Only 1100 more shopping days until the end of the World. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
